public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "allan at archlinux dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/57653] New: filename information discarded when using -imacros Date: Wed, 19 Jun 2013 14:16:00 -0000 [thread overview] Message-ID: <bug-57653-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57653 Bug ID: 57653 Summary: filename information discarded when using -imacros Product: gcc Version: 4.8.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: allan at archlinux dot org When compiling with the "-imacros" flag, the file name information is lost in error messages and backtraces. e.g. > gcc-4.8 -imacros i.h test.c <command-line>: In function ‘main’: <command-line>:5:1: error: expected ‘;’ before ‘}’ token The problem commit is: http://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=6adc88f8 >From gcc-bugs-return-424645-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jun 19 15:01:35 2013 Return-Path: <gcc-bugs-return-424645-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 5576 invoked by alias); 19 Jun 2013 15:01:35 -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 5534 invoked by uid 48); 19 Jun 2013 15:01:32 -0000 From: "meadori at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/57651] [4.8 / 4.9 Regression] gcc-ar and gcc-nm don't find the lto plugin Date: Wed, 19 Jun 2013 15:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: driver X-Bugzilla-Version: 4.8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: meadori at codesourcery dot com 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: Message-ID: <bug-57651-4-ynYbcKM7or@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-57651-4@http.gcc.gnu.org/bugzilla/> References: <bug-57651-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-06/txt/msg01024.txt.bz2 Content-length: 400 http://gcc.gnu.org/bugzilla/show_bug.cgi?idW651 --- Comment #2 from Meador Inge <meadori at codesourcery dot com> --- Since Jakub posted a patch for the PATH problem [1] and it seems that the permission issue might be a non-issue [2] is there anything else let for this bug? [1] http://gcc.gnu.org/ml/gcc-patches/2013-06/msg01122.html [2] http://gcc.gnu.org/ml/gcc-patches/2013-06/msg01113.html
next reply other threads:[~2013-06-19 14:16 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-06-19 14:16 allan at archlinux dot org [this message] 2013-06-19 22:30 ` [Bug c/57653] " manu at gcc dot gnu.org 2013-06-20 1:47 ` allan at archlinux dot org 2013-06-20 7:51 ` manu at gcc dot gnu.org 2013-06-23 7:18 ` allan at archlinux dot org 2013-06-23 12:04 ` allan at archlinux dot org 2013-06-23 13:49 ` manu at gcc dot gnu.org 2013-06-24 8:17 ` manu at gcc dot gnu.org 2013-06-25 0:21 ` allan at archlinux dot org 2013-06-25 8:30 ` manu at gcc dot gnu.org 2013-06-25 17:54 ` manu at gcc dot gnu.org 2013-06-26 8:48 ` manu at gcc dot gnu.org 2014-07-24 9:00 ` mpolacek at gcc dot gnu.org 2015-02-11 10:23 ` [Bug c/57653] [4.8/4.9 Regression] " rguenth at gcc dot gnu.org 2015-02-11 10:23 ` rguenth at gcc dot gnu.org 2015-02-11 12:14 ` rguenth at gcc dot gnu.org 2015-02-11 12:15 ` rguenth at gcc dot gnu.org 2015-02-11 12:15 ` rguenth at gcc dot gnu.org 2015-02-12 9:49 ` rguenth 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-57653-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).