public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/65751] Bogus &L in error message Date: Fri, 05 Jun 2015 09:58:00 -0000 [thread overview] Message-ID: <bug-65751-4-e5huTJpdIq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65751-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65751 Manuel López-Ibáñez <manu at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |manu at gcc dot gnu.org --- Comment #3 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to Thomas Koenig from comment #2) > And I think an English error message that points out the place of the error > is > more useful than a native-language one which doesn't, so I would favor > backporting. When backporting to GCC 5, this is probably gfc_error_1, however, it you remove one of the %L, then you can use gfc_error (and get the colors). >From gcc-bugs-return-488148-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jun 05 10:17:30 2015 Return-Path: <gcc-bugs-return-488148-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 70858 invoked by alias); 5 Jun 2015 10:17:29 -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 70798 invoked by uid 48); 5 Jun 2015 10:17:26 -0000 From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/66429] New: ICE in expand_GOMP_SIMD_LAST_LANE Date: Fri, 05 Jun 2015 10:17:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libgomp X-Bugzilla-Version: 6.0 X-Bugzilla-Keywords: 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone Message-ID: <bug-66429-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/msg00480.txt.bz2 Content-length: 2738 https://gcc.gnu.org/bugzilla/show_bug.cgi?idf429 Bug ID: 66429 Summary: ICE in expand_GOMP_SIMD_LAST_LANE Product: gcc Version: 6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libgomp Assignee: unassigned at gcc dot gnu.org Reporter: vries at gcc dot gnu.org CC: jakub at gcc dot gnu.org Target Milestone: --- Consider testcase libgomp/testsuite/libgomp.c/for-2.c. It starts with: ... /* { dg-options "-std=gnu99 -fopenmp" } */ ... I. When running the testcase, we see in the compilation line: ... -fopenmp -std=gnu99 -fopenmp ... The -fopenmp in dg-options is superfluous, because -fopenmp is forced in c.exp: ... # Turn on OpenMP. lappend ALWAYS_CFLAGS "additional_flags=-fopenmp" ... Removing the -fopenmp from dg-options gives us: ... -fopenmp -std=gnu99 ... II. The std=gnu99 is to support loop initial declarations, such as this one from for-2.h: ... for (unsigned int i = __INT_MAX__; i < 3000U + __INT_MAX__; i += 2) ... But the default C mode has changed from gnu89 to gnu11, so that setting is no longer needed. Using empty dg-options, the test still passes: ... PASS: libgomp.c/for-2.c (test for excess errors) PASS: libgomp.c/for-2.c execution test ... III. Removing the empty dg-options, brings the change that it's compiled with default option -O2, and we get an internal compiler error: ... FAIL: libgomp.c/for-2.c (internal compiler error) FAIL: libgomp.c/for-2.c (test for excess errors) UNRESOLVED: libgomp.c/for-2.c compilation failed to produce executable ... In more detail ... In file included from src/libgomp/testsuite/libgomp.c/for-1.h:8:0,^M from src/libgomp/testsuite/libgomp.c/for-2.c:18:^M src/libgomp/testsuite/libgomp.c/for-2.h: In function 'f12_pf_simd_static32._omp_fn.27':^M src/libgomp/testsuite/libgomp.c/for-2.h:153:9: internal compiler error: in expand_GOMP_SIMD_LAST_LANE, at internal-fn.c:190^M 0xbb4308 expand_GOMP_SIMD_LAST_LANE^M src/gcc/internal-fn.c:190^M 0xbbaeec expand_internal_call(gcall*)^M src/gcc/internal-fn.c:1996^M 0x864305 expand_call_stmt^M src/gcc/cfgexpand.c:2322^M 0x868656 expand_gimple_stmt_1^M src/gcc/cfgexpand.c:3266^M 0x868d98 expand_gimple_stmt^M src/gcc/cfgexpand.c:3420^M 0x872002 expand_gimple_basic_block^M src/gcc/cfgexpand.c:5432^M 0x873d1b execute^M src/gcc/cfgexpand.c:6051^M Please submit a full bug report,^M with preprocessed source if appropriate.^M Please include the complete backtrace with any bug report.^M See <http://gcc.gnu.org/bugs.html> for instructions.^M ...
prev parent reply other threads:[~2015-06-05 9:58 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-13 9:12 [Bug fortran/65751] New: " burnus at gcc dot gnu.org 2015-04-13 13:46 ` [Bug fortran/65751] " dominiq at lps dot ens.fr 2015-06-04 19:14 ` tkoenig at gcc dot gnu.org 2015-06-05 9:58 ` manu at gcc dot gnu.org [this message]
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-65751-4-e5huTJpdIq@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).