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 c/57653] filename information discarded when using -imacros Date: Sun, 23 Jun 2013 07:18:00 -0000 [thread overview] Message-ID: <bug-57653-4-IvqkOBgLH3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57653-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57653 --- Comment #8 from Allan McRae <allan at archlinux dot org> --- I really have no idea what I am looking for... but adding a breakpoint at linemap_add I see (reason, file): LC_ENTER "foo.c" LC_RENAME "<command-line>" LC_ENTER "/usr/include/stdc-predef.h" LC_LEAVE 0x0 LC_RENAME "foo.c" <- correct output printed here LC_LEAVE 0x0 LC_ENTER "foo.c" LC_RENAME "<command-line>" LC_ENTER "foo.h" LC_LEAVE 0x0 LC_ENTER "/usr/include/stdc-predef.h" LC_RENAME "foo.c" LC_LEAVE 0x0 <- incorrect output printed here LC_LEAVE 0x0 So it looks like it is not leaving "/usr/include/stdc-predef.h" at the right time so the wrong thing is being renamed?
next prev parent reply other threads:[~2013-06-23 7:18 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-06-19 14:16 [Bug middle-end/57653] New: " allan at archlinux dot org 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 [this message] 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-IvqkOBgLH3@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).