public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/64043] [5 Regression] ICE (segfault) with LTO: in tree_check/tree.h:2758 get_binfo_at_offset/tree.c:11914
Date: Tue, 16 Dec 2014 11:22:00 -0000 [thread overview]
Message-ID: <bug-64043-4-6XUWV9d3Gt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64043-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64043
--- Comment #11 from Andreas Schwab <schwab@linux-m68k.org> ---
This breaks ada:
$ gcc/gnatmake --GCC=gcc/xgcc --GNATBIND=gcc/gnatbind --GNATLINK=gcc/gnatlink
-cargs -Bgcc/ -largs '--GCC=gcc/xgcc -Bgcc' -margs
--RTS=ia64-suse-linux/./libada -f ../gcc/testsuite/gnat.dg/lto8.adb -gnatws
-flto -lm -o ./lto8.exe
gcc/xgcc -c -I../gcc/testsuite/gnat.dg/ -Bgcc/ --RTS=ia64-suse-linux/./libada
-gnatws -flto -lm -I- ../gcc/testsuite/gnat.dg/lto8.adb
gcc/xgcc -c -I../gcc/testsuite/gnat.dg/ -Bgcc/ --RTS=ia64-suse-linux/./libada
-gnatws -flto -lm -I- ../gcc/testsuite/gnat.dg/lto8_pkg.adb
gcc/gnatbind --RTS=ia64-suse-linux/./libada -x lto8.ali
gcc/gnatlink lto8.ali --GCC=gcc/xgcc -Bgcc -flto -o ./lto8.exe
../gcc/testsuite/gnat.dg/lto8_pkg.ads: In function ‘lto8_pkg___elabs’:
../gcc/testsuite/gnat.dg/lto8_pkg.ads:4:1: internal compiler error: in
expand_gimple_stmt_1, at cfgexpand.c:3420
package Lto8_Pkg is
^
0x400000000026d36f expand_gimple_stmt_1
../../gcc/cfgexpand.c:3420
0x400000000026e52f expand_gimple_stmt
../../gcc/cfgexpand.c:3447
0x400000000027014f expand_gimple_basic_block
../../gcc/cfgexpand.c:5280
0x400000000027453f execute
../../gcc/cfgexpand.c:5889
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.
lto-wrapper: fatal error: /usr/local/gcc/test/Build/gcc/xgcc returned 1 exit
status
>From gcc-bugs-return-470853-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 16 11:25:10 2014
Return-Path: <gcc-bugs-return-470853-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30117 invoked by alias); 16 Dec 2014 11:25:10 -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 30098 invoked by uid 48); 16 Dec 2014 11:25:05 -0000
From: "belagod at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/64328] New: addr_equal-1.c fails execution.
Date: Tue, 16 Dec 2014 11:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: belagod 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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter
Message-ID: <bug-64328-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/msg01860.txt.bz2
Content-length: 996
https://gcc.gnu.org/bugzilla/show_bug.cgi?idd328
Bug ID: 64328
Summary: addr_equal-1.c fails execution.
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: belagod at gcc dot gnu.org
FAIL: gcc.dg/addr_equal-1.c execution test
$ aarch64-none-elf-gcc
/work/dev/arm/src/gcc/gcc/testsuite/gcc.dg/addr_equal-1.c -O2 -lm -mcmodel=tiny
-fPIC -o foo.exe
fails on AArch64. This test was introduced by this patch:
https://gcc.gnu.org/ml/gcc-patches/2014-12/msg00613.html
The specific test that's failing is
if (!__builtin_constant_p (&def_var0 == &def_var1))
abort();
where def_var0 and def_var1 are globals declared in the same translation unit.
When compiled with fPIC, how much can we know about their addresses at
compile-time for the above test to pass? Is this test valid?
next prev parent reply other threads:[~2014-12-16 11:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 9:59 [Bug lto/64043] New: " burnus at gcc dot gnu.org
2014-12-02 21:04 ` [Bug lto/64043] " hubicka at gcc dot gnu.org
2014-12-02 21:08 ` hubicka at gcc dot gnu.org
2014-12-02 21:20 ` jason at gcc dot gnu.org
2014-12-12 15:41 ` burnus at gcc dot gnu.org
2014-12-12 15:43 ` burnus at gcc dot gnu.org
2014-12-12 19:01 ` hubicka at gcc dot gnu.org
2014-12-15 3:42 ` hubicka at gcc dot gnu.org
2014-12-15 22:36 ` hubicka at gcc dot gnu.org
2014-12-16 11:22 ` schwab@linux-m68k.org [this message]
2014-12-17 14:29 ` dominiq at lps dot ens.fr
2014-12-22 15:03 ` izamyatin at gmail dot com
2014-12-22 15:17 ` hubicka at ucw dot cz
2014-12-22 15:36 ` izamyatin at gmail dot com
2015-01-12 7:47 ` izamyatin at gmail dot com
2015-01-14 6:37 ` hubicka at gcc dot gnu.org
2015-01-29 7:17 ` hubicka 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-64043-4-6XUWV9d3Gt@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: link
Be 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).