public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/54139] [4.8 regression] some ARM Thumb-2 tests appear to be run on ARMv5TE hardware causing unhandled exceptions Date: Fri, 11 Jan 2013 18:02:00 -0000 [thread overview] Message-ID: <bug-54139-4-CQGW1BgFUy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54139-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54139 --- Comment #2 from Aldy Hernandez <aldyh at gcc dot gnu.org> 2013-01-11 18:01:57 UTC --- I have built a cross cc1/cc1plus with: blah/configure --enable-languages=c,c++ --target=armv5tel-unknown-linux-gnueabi but I get a totally different error on testsuite/gcc.target/arm/mmx-2.c, not the unrecognized __builtin_arm* errors reported. I get an IRA ice: cp /source_dir/gcc/testsuite/gcc.target/arm/mmx-2.c a.c ./cc1 -quiet -mcpu=iwmmxt -flax-vector-conversions -std=gnu99 a.c -I /tmp a.c: In function 'foo': a.c:166:1: internal compiler error: in find_costs_and_classes, at ira-costs.c:1710 } ^ 0x7a7fdf find_costs_and_classes /source/gcc/gcc/ira-costs.c:1709 0x7a8147 ira_costs() /source/gcc/gcc/ira-costs.c:2043 0x7a321c ira_build() /source/gcc/gcc/ira-build.c:3195 0x79bc0b ira /source/gcc/gcc/ira.c:4475 0x79bc0b rest_of_handle_ira /source/gcc/gcc/ira.c:4709 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <http://gcc.gnu.org/bugs.html> for instructions. Unrecognized __builtin* sound like -mcpu=iwmmxt is not being passed to the compiler command line. Can you try "make check-gcc RUNTESTFLAGS=arm.exp" in your build/gcc directory and attach the the entire gcc/testsuite/gcc/gcc.log file? And just for kicks, could you include the result from: /build_directory$ grep 'with options' config.status and /build_directory$ grep 'with options' gcc/config.status This would help enormously, as I don't have an armv5tel machine to test on. Thanks.
next prev parent reply other threads:[~2013-01-11 18:02 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-31 13:46 [Bug testsuite/54139] New: " mikpe at it dot uu.se 2012-08-16 11:06 ` [Bug testsuite/54139] " rguenth at gcc dot gnu.org 2012-09-19 14:12 ` rguenth at gcc dot gnu.org 2012-10-23 16:36 ` ramana at gcc dot gnu.org 2013-01-10 19:32 ` aldyh at gcc dot gnu.org 2013-01-11 18:02 ` aldyh at gcc dot gnu.org [this message] 2013-01-15 9:26 ` jakub at gcc dot gnu.org 2013-01-15 15:49 ` aldyh at gcc dot gnu.org 2013-01-15 16:33 ` janis at gcc dot gnu.org 2013-01-15 16:50 ` aldyh at redhat dot com 2013-01-15 16:52 ` aldyh at gcc dot gnu.org 2013-01-15 17:12 ` janis at gcc dot gnu.org 2013-01-15 17:16 ` aldyh 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-54139-4-CQGW1BgFUy@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).