public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ramana at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/49398] New: [4.7 ] bootstrap broken for arm-linux-gnueabi with thumb mode. Date: Tue, 14 Jun 2011 00:23:00 -0000 [thread overview] Message-ID: <bug-49398-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49398 Summary: [4.7 ] bootstrap broken for arm-linux-gnueabi with thumb mode. Product: gcc Version: 4.7.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: target AssignedTo: unassigned@gcc.gnu.org ReportedBy: ramana@gcc.gnu.org CC: rearnsha@arm.com, ramana@gcc.gnu.org, carrot@gcc.gnu.org, michael.hope@linaro.org Created attachment 24513 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24513 Original test case. Originally found by Michael Hope's bootstrap builds . Rev 174940 appears to break bootstrap for --target=arm-linux-gnueabi --with-cpu=cortex-a9 --with-fpu=neon --with-float=softfp --with-mode=thumb. Bootstrap fails during the build of libiberty - from Michaels' logs here. http://builds.linaro.org/toolchain/gcc-4.7~svn174981/logs/armv7l-maverick-cbuild130-ursa4-cortexa9r1/gcc-build.txt Bisecting using a cross-compiler lead me to this revision. The cross-compiler was configured as follows : /home/ramrad01/sources/fsf/trunk/configure --target=arm-linux-gnueabi --with-cpu=cortex-a9 --with-fpu=neon --with-float=softfp --enable-languages=c ramrad01@e102742:/work/cross-build/build-174940/gcc$ !./xgcc ./xgcc -B`pwd` -mthumb -g -O2 ~/Downloads/regex.i -S ../../../gcc-4.7~/libiberty/regex.c: In function ‘xre_search_2’: ../../../gcc-4.7~/libiberty/regex.c:4961:1: internal compiler error: in cselib_record_set, at cselib.c:2224 Please submit a full bug report, with preprocessed source if appropriate. ramrad01@e102742:/work/cross-build/build-174938/gcc$ !./xgcc ./xgcc -B`pwd` -mthumb -g -O2 ~/Downloads/regex.i -S ICE disappears without -g - (So not sure if 174940 is the cause or it just appears to trigger it) . cheers Ramana
next reply other threads:[~2011-06-14 0:23 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-06-14 0:23 ramana at gcc dot gnu.org [this message] 2011-06-14 0:24 ` [Bug target/49398] " ramana at gcc dot gnu.org 2011-06-14 0:38 ` ramana at gcc dot gnu.org 2011-06-14 12:49 ` [Bug target/49398] [4.7 Regression] " rguenth at gcc dot gnu.org 2011-06-16 13:51 ` ramana at gcc dot gnu.org 2011-07-08 11:11 ` ramana at gcc dot gnu.org
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=bug-49398-4@http.gcc.gnu.org/bugzilla/ \ --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).