public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/66714] New: gomp4: libgomp.oacc-c-c++-common/atomic_capture-1.c -g ICE Date: Tue, 30 Jun 2015 22:17:00 -0000 [thread overview] Message-ID: <bug-66714-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66714 Bug ID: 66714 Summary: gomp4: libgomp.oacc-c-c++-common/atomic_capture-1.c -g ICE Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug Assignee: unassigned at gcc dot gnu.org Reporter: vries at gcc dot gnu.org Target Milestone: --- With gomp-4_0-branch, when running target-libgomp testsuite with --target_board=unix/-O2/-g, we have: c.exp: ... FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/atomic_capture-1.c -DACC_DEVICE_TYPE_host_nonshm=1 -DACC_MEM_SHARED=0 (internal compiler error) FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/atomic_capture-1.c -DACC_DEVICE_TYPE_host_nonshm=1 -DACC_MEM_SHARED=0 (test for excess errors) FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/atomic_capture-1.c -DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 (internal compiler error) FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/atomic_capture-1.c -DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 (test for excess errors) ... c++.exp: ... FAIL: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/atomic_capture-1.c -DACC_DEVICE_TYPE_host_nonshm=1 -DACC_MEM_SHARED=0 (internal compiler error) FAIL: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/atomic_capture-1.c -DACC_DEVICE_TYPE_host_nonshm=1 -DACC_MEM_SHARED=0 (test for excess errors) FAIL: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/atomic_capture-1.c -DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 (internal compiler error) FAIL: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/atomic_capture-1.c -DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 (test for excess errors) ... In more detail: ... src/libgomp/testsuite/libgomp.oacc-c/../libgomp.oacc-c-c++-common/atomic_capture-1.c: In function ‘main._omp_fn.44’: src/libgomp/testsuite/libgomp.oacc-c/../libgomp.oacc-c-c++-common/atomic_capture-1.c:817:9: internal compiler error: Segmentation fault 0xebeb50 crash_signal src/gcc/toplev.c:380 0x92e939 loc_list_from_tree src/gcc/dwarf2out.c:14444 0x92ef5e loc_list_from_tree src/gcc/dwarf2out.c:14571 0x92f3e2 loc_list_from_tree src/gcc/dwarf2out.c:14645 0x92ef5e loc_list_from_tree src/gcc/dwarf2out.c:14571 0x93478c add_location_or_const_value_attribute src/gcc/dwarf2out.c:16088 0x940528 gen_variable_die src/gcc/dwarf2out.c:19277 0x946189 gen_decl_die src/gcc/dwarf2out.c:21028 0x94481d process_scope_var src/gcc/dwarf2out.c:20543 0x944896 decls_for_scope src/gcc/dwarf2out.c:20568 0x93c0c0 gen_subprogram_die src/gcc/dwarf2out.c:18869 0x945e09 gen_decl_die src/gcc/dwarf2out.c:20961 0x94708c dwarf2out_decl src/gcc/dwarf2out.c:21394 0x9470ae dwarf2out_function_decl src/gcc/dwarf2out.c:21402 0x9ecc5b rest_of_handle_final src/gcc/final.c:4525 0x9ecfce execute src/gcc/final.c:4567 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. ... >From gcc-bugs-return-491101-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jun 30 22:23:13 2015 Return-Path: <gcc-bugs-return-491101-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 64953 invoked by alias); 30 Jun 2015 22:23:12 -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 64926 invoked by uid 48); 30 Jun 2015 22:23:08 -0000 From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/66714] gomp4: libgomp.oacc-c-c++-common/atomic_capture-1.c -g ICE Date: Tue, 30 Jun 2015 22:23:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: debug X-Bugzilla-Version: unknown X-Bugzilla-Keywords: ice-on-valid-code, openacc X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: 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: Message-ID: <bug-66714-4-5odn1cmN9S@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-66714-4@http.gcc.gnu.org/bugzilla/> References: <bug-66714-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: 2015-06/txt/msg03433.txt.bz2 Content-length: 1911 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66714 --- Comment #1 from vries at gcc dot gnu.org --- For c.exp, at -Ofast/-g, this failure looks similar: ... FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/reduction-1.c -DACC_DEVICE_TYPE_host_nonshm=1 -DACC_MEM_SHARED=0 (internal compiler error) FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/reduction-1.c -DACC_DEVICE_TYPE_host_nonshm=1 -DACC_MEM_SHARED=0 (test for excess errors) ... In more detail: ... src/libgomp/testsuite/libgomp.oacc-c/../libgomp.oacc-c-c++-common/reduction-1.c: In function ‘test_reductions_minmax._omp_fn.6’: src/libgomp/testsuite/libgomp.oacc-c/../libgomp.oacc-c-c++-common/reduction-1.c:96:1: internal compiler error: Segmentation fault 0xebeb50 crash_signal src/gcc/toplev.c:380 0x92e939 loc_list_from_tree src/gcc/dwarf2out.c:14444 0x92ef5e loc_list_from_tree src/gcc/dwarf2out.c:14571 0x92f3e2 loc_list_from_tree src/gcc/dwarf2out.c:14645 0x92ef5e loc_list_from_tree src/gcc/dwarf2out.c:14571 0x93478c add_location_or_const_value_attribute src/gcc/dwarf2out.c:16088 0x940528 gen_variable_die src/gcc/dwarf2out.c:19277 0x946189 gen_decl_die src/gcc/dwarf2out.c:21028 0x94481d process_scope_var src/gcc/dwarf2out.c:20543 0x944896 decls_for_scope src/gcc/dwarf2out.c:20568 0x93c0c0 gen_subprogram_die src/gcc/dwarf2out.c:18869 0x945e09 gen_decl_die src/gcc/dwarf2out.c:20961 0x94708c dwarf2out_decl src/gcc/dwarf2out.c:21394 0x9470ae dwarf2out_function_decl src/gcc/dwarf2out.c:21402 0x9ecc5b rest_of_handle_final src/gcc/final.c:4525 0x9ecfce execute src/gcc/final.c:4567 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. ... >From gcc-bugs-return-491102-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jun 30 22:36:52 2015 Return-Path: <gcc-bugs-return-491102-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 95539 invoked by alias); 30 Jun 2015 22:36:52 -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 95496 invoked by uid 48); 30 Jun 2015 22:36:48 -0000 From: "kkojima at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/64833] [SH]: Error: pcrel too far when compiling imagemagick and graphicsmagick on Debian sh4 Date: Tue, 30 Jun 2015 22:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 4.9.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kkojima at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: 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: Message-ID: <bug-64833-4-ZqdjN0VaXS@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-64833-4@http.gcc.gnu.org/bugzilla/> References: <bug-64833-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: 2015-06/txt/msg03434.txt.bz2 Content-length: 868 https://gcc.gnu.org/bugzilla/show_bug.cgi?idd833 --- Comment #20 from Kazumoto Kojima <kkojima at gcc dot gnu.org> --- (In reply to Oleg Endo from comment #17) > Increasing insn lengths unnecessarily might result in some unlucky constant > pool placements and far branches and some code might get worse. On the > other hand, constant pool placement and far branch code generation is "a > matter of luck" anyway. The tests for the patch in c#16 has been done successfully on trunk. On second thought, you are right about "a matter of luck" which is proved by this corner case bug itself reproduced only with rather exotic options. Even the patch doesn't affect existing codes, a tiny change of options or environment variables will perturb the results. I'll apply the patch in c#16 on trunk and backport it to 4.9/5 if the usual tests are OK for those branches.
next reply other threads:[~2015-06-30 22:17 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-30 22:17 vries at gcc dot gnu.org [this message] 2015-07-02 11:11 ` [Bug debug/66714] " vries at gcc dot gnu.org 2015-07-02 11:21 ` vries at gcc dot gnu.org 2015-07-02 11:26 ` vries at gcc dot gnu.org 2015-07-02 11:32 ` vries at gcc dot gnu.org 2015-07-02 11:35 ` vries at gcc dot gnu.org 2015-07-02 11:39 ` vries at gcc dot gnu.org 2015-07-02 11:46 ` vries at gcc dot gnu.org 2015-07-02 11:58 ` vries at gcc dot gnu.org 2015-07-02 12:00 ` vries at gcc dot gnu.org 2015-07-04 8:26 ` vries at gcc dot gnu.org 2015-07-04 8:34 ` [Bug debug/66714] ICE in loc_list_from_tree with -g vries at gcc dot gnu.org 2015-07-06 7:44 ` vries at gcc dot gnu.org 2015-07-06 7:50 ` vries at gcc dot gnu.org 2015-07-06 7:56 ` [Bug libgomp/66714] " vries at gcc dot gnu.org 2015-07-06 9:34 ` vries at gcc dot gnu.org 2015-07-06 9:35 ` vries at gcc dot gnu.org 2015-07-09 11:12 ` vries at gcc dot gnu.org 2015-07-21 22:27 ` cesar at gcc dot gnu.org 2015-07-21 22:47 ` vries at gcc dot gnu.org 2015-07-22 2:15 ` cesar at gcc dot gnu.org 2015-07-22 23:36 ` cesar at gcc dot gnu.org 2015-07-24 14:39 ` cesar at gcc dot gnu.org 2015-07-27 14:29 ` cesar 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-66714-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).