public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amker at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/64348] New: Case scal-to-vec1.c failed on arm-linux-gnueabi with -fPIC Date: Thu, 18 Dec 2014 08:38:00 -0000 [thread overview] Message-ID: <bug-64348-4@http.gcc.gnu.org/bugzilla/> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 6855 bytes --] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64348 Bug ID: 64348 Summary: Case scal-to-vec1.c failed on arm-linux-gnueabi with -fPIC Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: amker at gcc dot gnu.org Case scal-to-vec1.c failed because of ICE on arm-linux-gnueabi with -fPIC. The compilation command line is: ./arm-none-linux-gnueabi-gcc scal-to-vec1.c -fno-diagnostics-show-caret -fdiagnostics-color=never -O3 -S -fPIC -o ./scal-to-vec1.S -mcpu=cortex-a8/a9 -marm Thumb mode is fine, processors like cortex-a7/a15 are fine. The ICE info is like below: /home/binche01/work/oban-work/src/gcc/gcc/testsuite/gcc.c-torture/execute/scal-to-vec1.c: In function âmainâ: /home/binche01/work/oban-work/src/gcc/gcc/testsuite/gcc.c-torture/execute/scal-to-vec1.c:86:1: internal compiler error: in split_reg, at lra-constraints.c:4879 0xbad893 split_reg /home/binche01/work/oban-work/src/gcc/gcc/lra-constraints.c:4879 0xbade33 split_if_necessary /home/binche01/work/oban-work/src/gcc/gcc/lra-constraints.c:4983 0xbafb13 inherit_in_ebb /home/binche01/work/oban-work/src/gcc/gcc/lra-constraints.c:5478 0xbb04fc lra_inheritance() /home/binche01/work/oban-work/src/gcc/gcc/lra-constraints.c:5639 0xb9914b lra(_IO_FILE*) /home/binche01/work/oban-work/src/gcc/gcc/lra.c:2303 0xb48738 do_reload /home/binche01/work/oban-work/src/gcc/gcc/ira.c:5402 0xb48b0e execute /home/binche01/work/oban-work/src/gcc/gcc/ira.c:5573 Gcc is configured as below: --target=arm-none-linux-gnueabi --prefix=... --with-sysroot=... --disable-libssp --disable-libmudflap --enable-checking=yes --enable-languages=c,c++ --with-gmp=... --with-mpfr=... --with-mpc=... --with-isl=... --with-cloog=... --disable-libgomp --with-arch=armv7-a It is from thread https://gcc.gnu.org/ml/gcc-patches/2014-09/msg01448.html File this PR for tracking. >From gcc-bugs-return-471057-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 18 09:26:48 2014 Return-Path: <gcc-bugs-return-471057-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 12668 invoked by alias); 18 Dec 2014 09:26:48 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 12644 invoked by uid 48); 18 Dec 2014 09:26:43 -0000 From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/64244] [4.8/4.9/5 Regression] ICE at class.c:236 when using non_overridable Date: Thu, 18 Dec 2014 09:26:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 4.9.2 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: janus at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: janus at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-64244-4-VQaYotA1U1@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-64244-4@http.gcc.gnu.org/bugzilla/> References: <bug-64244-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-12/txt/msg02064.txt.bz2 Content-length: 509 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64244 --- Comment #15 from janus at gcc dot gnu.org --- (In reply to OndÅej ÄertÃk from comment #14) > I tested it and it seems to be working! The code compiled with > non_overridable on. Great. Thanks for checking. > There are run-time segfaults and array bounds mismatches in our code, > that don't happen with ifort, so I will be slowly isolating those and > reporting them. That would be very helpful (please use separate PRs for those). >From gcc-bugs-return-471058-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 18 09:31:48 2014 Return-Path: <gcc-bugs-return-471058-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 15221 invoked by alias); 18 Dec 2014 09:31:48 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 15164 invoked by uid 48); 18 Dec 2014 09:31:45 -0000 From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/64344] [5 Regression] [UBSAN] ICE with -fsanitize=float-cast-overflow [ICE in -fsanitize=float-cast-overflow] Date: Thu, 18 Dec 2014 09:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created Message-ID: <bug-64344-4-I0wnvf2CGd@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-64344-4@http.gcc.gnu.org/bugzilla/> References: <bug-64344-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-12/txt/msg02065.txt.bz2 Content-length: 527 https://gcc.gnu.org/bugzilla/show_bug.cgi?idd344 --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Created attachment 34297 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id4297&actioníit gcc5-pr64344.patch Untested fix, but this is getting way too ugly. Furthermore, e.g. void bar (void) { static const int a = 0.5; static const int b = 1e234; } still fails with C. Wonder what was the reason to instrument it so early, supposedly to not miss conversions optimized away during folding, right?
next reply other threads:[~2014-12-18 8:38 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-18 8:38 amker at gcc dot gnu.org [this message] 2014-12-18 10:21 ` [Bug target/64348] [5 Regression] " rguenth at gcc dot gnu.org 2014-12-20 9:21 ` amker at gcc dot gnu.org 2015-01-09 6:20 ` amker at gcc dot gnu.org 2015-01-13 10:27 ` rguenth at gcc dot gnu.org 2015-01-13 10:51 ` amker 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-64348-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).