public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "justinmattock at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/43791] kernel/rtmutex.c:1138:1: internal compiler error: in cgraph_decide_inlining_of_small_functions, at ipa-inline.c:1009 Date: Mon, 19 Apr 2010 07:14:00 -0000 [thread overview] Message-ID: <20100419071352.13262.qmail@sourceware.org> (raw) In-Reply-To: <bug-43791-17596@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from justinmattock at gmail dot com 2010-04-19 07:13 ------- Created an attachment (id=20414) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=20414&action=view) kernel .config here is my .config I used to hit this error, and FWIW here is my compile flags that I used for gcc: CFLAGS="-m64 -mtune=core2 -march=core2 -O2 -pipe -fomit-frame-pointer" CXXFLAGS="${CFLAGS}" MAKEOPTS="{-j3}" ../gcc*/configure --prefix=/usr --libexecdir=/usr/lib --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-c99 --enable-long-long --enable-clocale=gnu --enable-languages=c,c++ --disable-multilib --disable-libstdcxx-pch is there a git repository for gcc? right now I'm seeing: http://git.infradead.org/gcc.git if this is then I can try a bisect on with gcc(but then again might be tricky with the need for a pure64 patch). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43791
next prev parent reply other threads:[~2010-04-19 7:14 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-04-19 6:41 [Bug other/43791] New: " justinmattock at gmail dot com 2010-04-19 7:14 ` justinmattock at gmail dot com [this message] 2010-04-19 7:24 ` [Bug other/43791] " jiez at gcc dot gnu dot org 2010-04-19 14:26 ` justinmattock at gmail dot com 2010-04-19 19:44 ` justinmattock at gmail dot com 2010-04-19 19:52 ` hjl dot tools at gmail dot com 2010-04-19 19:55 ` justinmattock at gmail dot com 2010-04-19 20:26 ` [Bug tree-optimization/43791] " falk at debian dot org 2010-04-19 20:48 ` justinmattock at gmail dot com 2010-04-19 21:08 ` hjl dot tools at gmail dot com 2010-04-19 22:40 ` justinmattock at gmail dot com 2010-04-20 0:16 ` justinmattock at gmail dot com 2010-04-20 0:18 ` justinmattock at gmail dot com 2010-04-20 8:59 ` [Bug tree-optimization/43791] [4.6 Regression] " rguenth at gcc dot gnu dot org 2010-04-20 9:11 ` justinmattock at gmail dot com 2010-04-21 1:12 ` justinmattock at gmail dot com 2010-04-21 20:24 ` rguenth at gcc dot gnu dot org 2010-04-22 18:40 ` djdragonboy at gmail dot com 2010-04-24 6:35 ` justinmattock at gmail dot com 2010-04-26 2:41 ` justinmattock at gmail dot com 2010-05-06 3:58 ` hjl dot tools at gmail dot com 2010-05-06 13:12 ` hubicka at gcc dot gnu dot org 2010-05-06 13:17 ` rogutes at googlemail dot com 2010-05-06 13:20 ` rogutes at googlemail dot com 2010-05-06 13:28 ` justinmattock at gmail dot com 2010-05-06 13:31 ` justinmattock at gmail dot com 2010-05-06 13:44 ` justinmattock at gmail dot com 2010-05-06 13:51 ` hubicka at ucw dot cz 2010-05-06 14:16 ` hubicka at gcc dot gnu dot org 2010-05-06 14:37 ` justinmattock at gmail dot com 2010-05-08 8:02 ` justinmattock at gmail dot com 2010-05-08 9:23 ` hubicka at ucw dot cz 2010-05-08 15:33 ` justinmattock at gmail dot com 2010-07-23 11:42 ` rguenth at gcc dot gnu dot org 2010-07-23 13:27 ` justinmattock at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20100419071352.13262.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).