gcc- 4.6.0 20100416 rtmutex.c:1138:1: internal compiler error
in [Kernel]
|
Prev: tracing: Dump either the oops's cpu source or all cpus buffers
Next: [PATCH] hugetlbfs: Kill applications that use MAP_NORESERVE with SIGBUS instead of OOM-killer
From: Justin P. Mattock on 19 Apr 2010 03:30 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Jonathan Wakely on 19 Apr 2010 17:20 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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Justin P. Mattock on 19 Apr 2010 17:40
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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |