public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/59379] [4.9 Regression] gomp_init_num_threads is compiled into an infinite loop with --with-arch=corei7 --with-cpu=slm Date: Wed, 04 Dec 2013 23:39:00 -0000 [thread overview] Message-ID: <bug-59379-4-t7CAFpspsS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59379-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59379 --- Comment #7 from H.J. Lu <hjl.tools at gmail dot com> --- r202807 can bootstrap. But r202811 failed with [hjl@gnu-mic-2 libgcc]$ /export/build/gnu/gcc-lto-fdo/build-x86_64-linux/./gcc/xgcc -B/export/build/gnu/gcc-lto-fdo/build-x86_64-linux/./gcc/ -B/usr/local/x86_64-unknown-linux-gnu/bin/ -B/usr/local/x86_64-unknown-linux-gnu/lib/ -isystem /usr/local/x86_64-unknown-linux-gnu/include -isystem /usr/local/x86_64-unknown-linux-gnu/sys-include -g -O2 -m32 -O2 -g -O2 -DIN_GCC -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem ./include -fpic -mlong-double-80 -g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector -fpic -mlong-double-80 -I. -I. -I../../.././gcc -I/export/gnu/import/git/gcc/libgcc -I/export/gnu/import/git/gcc/libgcc/. -I/export/gnu/import/git/gcc/libgcc/../gcc -I/export/gnu/import/git/gcc/libgcc/../include -I/export/gnu/import/git/gcc/libgcc/config/libbid -DENABLE_DECIMAL_BID_FORMAT -DHAVE_CC_TLS -DUSE_TLS -o unwind-dw2-fde-dip.o -MT unwind-dw2-fde-dip.o -MD -MP -MF unwind-dw2-fde-dip.dep -fexceptions -c /export/gnu/import/git/gcc/libgcc/unwind-dw2-fde-dip.c -fvisibility=hidden -DHIDE_EXPORTS In file included from /export/gnu/import/git/gcc/libgcc/unwind-dw2-fde-dip.c:89:0: /export/gnu/import/git/gcc/libgcc/unwind-dw2-fde.c: In function ‘classify_object_over_fdes’: /export/gnu/import/git/gcc/libgcc/unwind-dw2-fde.c:660:1: internal compiler error: Segmentation fault } ^ 0x5eb5ce crash_signal /export/gnu/import/git/gcc/gcc/toplev.c:335 0x931cb3 htab_find_slot_with_hash /export/gnu/import/git/gcc/libiberty/hashtab.c:655 0x931cb3 gen_rtx_CONST_INT /export/gnu/import/git/gcc/gcc/emit-rtl.c:410 0x931cb3 gen_int_mode /export/gnu/import/git/gcc/gcc/emit-rtl.c:420 0x931cb3 get_mode_bounds(machine_mode, int, machine_mode, rtx_def**, rtx_def**) /export/gnu/import/git/gcc/gcc/stor-layout.c:2840 0x95245e simplify_const_relational_operation(rtx_code, machine_mode, rtx_def*, rtx_def*) /export/gnu/import/git/gcc/gcc/simplify-rtx.c:5151 0x9525ab simplify_const_relational_operation(rtx_code, machine_mode, rtx_def*, rtx_def*) /export/gnu/import/git/gcc/gcc/simplify-rtx.c:5006 0x95b364 simplify_relational_operation(rtx_code, machine_mode, machine_mode, rtx_def*, rtx_def*) /export/gnu/import/git/gcc/gcc/simplify-rtx.c:4602 0x7a6dd2 fold_rtx /export/gnu/import/git/gcc/gcc/cse.c:3378 0x7a7046 fold_rtx /export/gnu/import/git/gcc/gcc/cse.c:3209 0x7aa6aa cse_insn /export/gnu/import/git/gcc/gcc/cse.c:4578 0x7af736 cse_extended_basic_block /export/gnu/import/git/gcc/gcc/cse.c:6410 0x7af736 cse_main(rtx_def*, int) [clone .isra.18] /export/gnu/import/git/gcc/gcc/cse.c:6588 0xf5394b rest_of_handle_cse /export/gnu/import/git/gcc/gcc/cse.c:7438 0xf5394b (anonymous namespace)::pass_cse::execute() [clone .lto_priv.9491] /export/gnu/import/git/gcc/gcc/cse.c:7484 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. The only difference in GCC source is: diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 0f54f2b..b7c5255 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20130920 +20130921 >From gcc-bugs-return-436687-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 23:53:41 2013 Return-Path: <gcc-bugs-return-436687-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 7014 invoked by alias); 4 Dec 2013 23:53:41 -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 6967 invoked by uid 48); 4 Dec 2013 23:53:38 -0000 From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/59388] [4.7/4.8/4.9 Regression] ICE on valid code at -O1 and above on x86_64-linux-gnu Date: Wed, 04 Dec 2013 23:53:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc short_desc Message-ID: <bug-59388-4-1rNqHT7vZV@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-59388-4@http.gcc.gnu.org/bugzilla/> References: <bug-59388-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: 2013-12/txt/msg00342.txt.bz2 Content-length: 681 http://gcc.gnu.org/bugzilla/show_bug.cgi?idY388 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org Summary|[4.9 Regression] ICE on |[4.7/4.8/4.9 Regression] |valid code at -O1 and above |ICE on valid code at -O1 |on x86_64-linux-gnu |and above on | |x86_64-linux-gnu --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Likely introduced in r179388.
next prev parent reply other threads:[~2013-12-04 23:39 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-03 21:40 [Bug target/59379] New: " hjl.tools at gmail dot com 2013-12-03 21:46 ` [Bug target/59379] " octoploid at yandex dot com 2013-12-03 21:51 ` hjl.tools at gmail dot com 2013-12-03 21:52 ` hjl.tools at gmail dot com 2013-12-04 0:41 ` hjl.tools at gmail dot com 2013-12-04 0:48 ` hjl.tools at gmail dot com 2013-12-04 10:52 ` [Bug target/59379] [4.9 Regression] " hjl.tools at gmail dot com 2013-12-04 23:39 ` hjl.tools at gmail dot com [this message] 2013-12-05 3:11 ` hjl.tools at gmail dot com 2013-12-05 11:17 ` rguenth at gcc dot gnu.org 2013-12-06 1:45 ` hjl.tools at gmail dot com 2013-12-19 15:37 ` rguenth at gcc dot gnu.org 2013-12-26 12:41 ` izamyatin at gmail dot com 2013-12-26 12:57 ` hjl.tools at gmail dot com 2013-12-26 14:41 ` hjl.tools at gmail dot com 2013-12-30 21:16 ` izamyatin at gmail dot com 2013-12-31 7:02 ` izamyatin at gmail dot com 2014-01-18 17:13 ` hjl.tools at gmail dot com 2014-01-18 19:47 ` ubizjak at gmail dot com 2014-01-19 9:51 ` ubizjak at gmail dot com 2014-01-19 14:18 ` hjl.tools at gmail dot com 2014-01-19 15:48 ` uros at gcc dot gnu.org 2014-01-22 18:29 ` uros at gcc dot gnu.org 2014-01-22 18:40 ` ubizjak 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=bug-59379-4-t7CAFpspsS@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).