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 c/57653] filename information discarded when using -imacros
Date: Wed, 26 Jun 2013 08:48:00 -0000	[thread overview]
Message-ID: <bug-57653-4-3skUvYjRCL@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

Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jsm28 at gcc dot gnu.org

--- Comment #20 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
(In reply to Allan McRae from comment #19)
> That patch works.  With -imacros foo.h:
> 
> LC_ENTER  foo.c
> LC_RENAME <command-line>
> LC_ENTER  foo.h
> LC_LEAVE  0x0
> LC_ENTER  /usr/include/stdc-predef.h
> LC_LEAVE  0x0
> LC_RENAME foo.c
> <- correct output
> LC_LEAVE  0x0
> 
> All other combinations of -include/-imacros/-ffreestanding/no foo.h  all are
> unchanged as expected.

Great! I am certainly too busy at the moment to go through all the steps of the
contribution process for this. The patch needs to be fully bootstrapped with
the latest trunk, an appropriate testcase needs to be created, plus run the
full regression testsuite and compare the results with the regression results
of the unpatched trunk and check that no new failures appear. Then, it has to
be submitted to gcc-patches with a GNU Changelog.

If you are really interested in fixing this, you should just take the lead.
Feel free to modify the patch as you need. The patch is anyway too small to
require any kind of legal assignment, but if they ask for it, you can always
say I wrote it. I have an assignment in place with the FSF.

When submitting to gcc-patches, CC jsm28@gcc.gnu.org. You can also see in the
svn log or svn blame who wrote the -imacro code and CC him/her as well. (You
can also CC me).
>From gcc-bugs-return-425166-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jun 26 08:49:39 2013
Return-Path: <gcc-bugs-return-425166-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15787 invoked by alias); 26 Jun 2013 08:49:39 -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 15751 invoked by uid 48); 26 Jun 2013 08:49:36 -0000
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/57653] filename information discarded when using -imacros
Date: Wed, 26 Jun 2013 08:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 4.8.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: manu at gcc dot gnu.org
X-Bugzilla-Status: NEW
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-57653-4-PkcVYuSRK3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-57653-4@http.gcc.gnu.org/bugzilla/>
References: <bug-57653-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: 2013-06/txt/msg01545.txt.bz2
Content-length: 237

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57653

--- Comment #21 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
Once you are in trunk, you can ask the release managers to backport it to the
GCC 4.8 branch.
>From gcc-bugs-return-425167-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jun 26 09:07:49 2013
Return-Path: <gcc-bugs-return-425167-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26857 invoked by alias); 26 Jun 2013 09:07:48 -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 26829 invoked by uid 48); 26 Jun 2013 09:07:41 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/57712] GCC fails to to match out-of-line template member function definition with declaration
Date: Wed, 26 Jun 2013 09:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.8.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
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_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-57712-4-hrZsYPblWM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-57712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-57712-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/msg01546.txt.bz2
Content-length: 400

http://gcc.gnu.org/bugzilla/show_bug.cgi?idW712

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2013-06-26
     Ever confirmed|0                           |1


  parent reply	other threads:[~2013-06-26  8:48 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
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 [this message]
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-3skUvYjRCL@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: link
Be 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).