so far I've compiled most of the system
(glibc,Xserver,etc..)
and not really anything has crashed and burned
except for the kernel:
kernel/rtmutex.c: At top level:
kernel/rtmutex.c:1138:1: internal compiler error: in
cgraph_decide_inlining_of_small_functions, at ipa-inline.c:1009
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
make[1]: *** [kernel/rtmutex.o] Error 1
make: *** [kernel] Error 2
any reports of this/ideas?
--
Justin P. Mattock
On 04/19/2010 12:19 PM, Justin Mattock wrote:
> so far I've compiled most of the system
> (glibc,Xserver,etc..)
> and not really anything has crashed and burned
> except for the kernel:
>
> kernel/rtmutex.c: At top level:
> kernel/rtmutex.c:1138:1: internal compiler error: in
> cgraph_decide_inlining_of_small_functions, at ipa-inline.c:1009
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See<http://gcc.gnu.org/bugs.html> for instructions.
> make[1]: *** [kernel/rtmutex.o] Error 1
> make: *** [kernel] Error 2
>
> any reports of this/ideas?
>
Please report a bug with a preprocessed source file in GCC's bugzilla.
--
Jie Zhang
CodeSourcery
(650) 331-3385 x735
On Sun, 18 Apr 2010 21:19:19 -0700, Justin Mattock <[email protected]> wrote:
> so far I've compiled most of the system
> (glibc,Xserver,etc..)
> and not really anything has crashed and burned
> except for the kernel:
>
You are using a pre-release compiler. It should be no surprise that it chokes
on the kernel. You should do as the compiler said and report this to the gcc
folks.
- Ben
On 04/18/2010 10:35 PM, Ben Gamari wrote:
> On Sun, 18 Apr 2010 21:19:19 -0700, Justin Mattock<[email protected]> wrote:
>> so far I've compiled most of the system
>> (glibc,Xserver,etc..)
>> and not really anything has crashed and burned
>> except for the kernel:
>>
> You are using a pre-release compiler. It should be no surprise that it chokes
> on the kernel. You should do as the compiler said and report this to the gcc
> folks.
>
> - Ben
>
>
I couldn't resist..(had to play),
anyways I looked through the reports
but didn't see anything that was
familiar. so I went and created an entry:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43791
Justin P. Mattock
On 04/19/2010 02:43 PM, Justin P. Mattock wrote:
> I couldn't resist..(had to play),
> anyways I looked through the reports
> but didn't see anything that was
> familiar. so I went and created an entry:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43791
>
Thanks. Please add a preprocessed source file so people can reproduce
your issue.
--
Jie Zhang
CodeSourcery
(650) 331-3385 x735
On 04/18/2010 11:57 PM, Jie Zhang wrote:
> On 04/19/2010 02:43 PM, Justin P. Mattock wrote:
>> I couldn't resist..(had to play),
>> anyways I looked through the reports
>> but didn't see anything that was
>> familiar. so I went and created an entry:
>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43791
>>
> Thanks. Please add a preprocessed source file so people can reproduce
> your issue.
>
>
as for the preprocessed source file,
not that yet skilled at code.(one day)
I added my .config, and the CFLAGS
I used for building gcc.
In regards to 4.6.0 everything seems
o.k. i.g. glibc builds with no errors
all of the xserver no errors, even firefox
builds.. seems the kernel was the only real
problem I ran into(which isn't really a problem
given this version of gcc is experimental).
maybe something todo with building modules
(but could be wrong).
Justin P. Mattock
On 19 April 2010 08:20, Justin P. Mattock wrote:
> On 04/18/2010 11:57 PM, Jie Zhang wrote:
>>
>> On 04/19/2010 02:43 PM, Justin P. Mattock wrote:
>>>
>>> I couldn't resist..(had to play),
>>> anyways I looked through the reports
>>> but didn't see anything that was
>>> familiar. so I went and created an entry:
>>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43791
>>>
>> Thanks. Please add a preprocessed source file so people can reproduce
>> your issue.
>>
>>
>
>
> as for the preprocessed source file,
> not that yet skilled at code.(one day)
See the "how to report" link on the gcc front page:
http://gcc.gnu.org/bugs/
It's not hard.
On 04/19/2010 02:17 PM, Jonathan Wakely wrote:
> On 19 April 2010 08:20, Justin P. Mattock wrote:
>> On 04/18/2010 11:57 PM, Jie Zhang wrote:
>>>
>>> On 04/19/2010 02:43 PM, Justin P. Mattock wrote:
>>>>
>>>> I couldn't resist..(had to play),
>>>> anyways I looked through the reports
>>>> but didn't see anything that was
>>>> familiar. so I went and created an entry:
>>>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43791
>>>>
>>> Thanks. Please add a preprocessed source file so people can reproduce
>>> your issue.
>>>
>>>
>>
>>
>> as for the preprocessed source file,
>> not that yet skilled at code.(one day)
>
> See the "how to report" link on the gcc front page:
> http://gcc.gnu.org/bugs/
> It's not hard.
>
the info from jie, worked, as well
as: make kernel/rtmutex.i
(from joe perches)
Justin P. Mattock