public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "markus at trippelsdorf dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug pch/53880] [4.8 Regression] compile time regression when generating precompiled headers for boost
Date: Tue, 31 Jul 2012 10:36:00 -0000 [thread overview]
Message-ID: <bug-53880-4-qeLSKixdOx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53880-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53880
Markus Trippelsdorf <markus at trippelsdorf dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
--- Comment #34 from Markus Trippelsdorf <markus at trippelsdorf dot de> 2012-07-31 10:35:54 UTC ---
(In reply to comment #33)
> Fixed for GCC 4.8.0.
>
> It would be nice to know what the effect of the patch is for GCC 4.7, but I
> don't have things set up to test that. Markus, if you can do that testing, I'm
> interested in the results. Otherwise, this PR can be closed as FIXED.
Given that -ftrack-macro-expansion is zero by default for GCC-4.7
there is no regression to fix AFAICS. So IMHO this patch shouldn't
be applied on the 4.7 branch. (It would only be relevant if one
explicitly uses the -ftrack-macro-expansion=2 when generating the pch.)
prev parent reply other threads:[~2012-07-31 10:36 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 15:46 [Bug pch/53880] New: " markus at trippelsdorf dot de
2012-07-06 15:55 ` [Bug pch/53880] " markus at trippelsdorf dot de
2012-07-06 16:47 ` markus at trippelsdorf dot de
2012-07-08 7:08 ` markus at trippelsdorf dot de
2012-07-09 8:41 ` rguenth at gcc dot gnu.org
2012-07-23 13:46 ` paolo.carlini at oracle dot com
2012-07-23 21:29 ` steven at gcc dot gnu.org
2012-07-23 22:46 ` steven at gcc dot gnu.org
2012-07-24 6:50 ` markus at trippelsdorf dot de
2012-07-24 8:16 ` stevenb.gcc at gmail dot com
2012-07-24 9:20 ` steven at gcc dot gnu.org
2012-07-24 9:34 ` rguenth at gcc dot gnu.org
2012-07-24 9:41 ` stevenb.gcc at gmail dot com
2012-07-24 9:43 ` rguenth at gcc dot gnu.org
2012-07-24 10:03 ` stevenb.gcc at gmail dot com
2012-07-24 10:13 ` paolo.carlini at oracle dot com
2012-07-26 16:30 ` dodji at seketeli dot org
2012-07-26 17:15 ` dodji at seketeli dot org
2012-07-26 17:16 ` dodji at seketeli dot org
2012-07-26 17:16 ` dodji at seketeli dot org
2012-07-26 17:18 ` dodji at seketeli dot org
2012-07-26 19:45 ` stevenb.gcc at gmail dot com
2012-07-26 21:11 ` dodji at seketeli dot org
2012-07-30 9:11 ` steven at gcc dot gnu.org
2012-07-30 10:54 ` markus at trippelsdorf dot de
2012-07-30 11:08 ` steven at gcc dot gnu.org
2012-07-30 11:22 ` markus at trippelsdorf dot de
2012-07-30 12:03 ` steven at gcc dot gnu.org
2012-07-30 13:17 ` steven at gcc dot gnu.org
2012-07-30 13:52 ` steven at gcc dot gnu.org
2012-07-30 14:22 ` steven at gcc dot gnu.org
2012-07-30 15:04 ` steven at gcc dot gnu.org
2012-07-30 16:15 ` steven at gcc dot gnu.org
2012-07-30 16:26 ` markus at trippelsdorf dot de
2012-07-30 22:55 ` steven at gcc dot gnu.org
2012-07-31 9:21 ` steven at gcc dot gnu.org
2012-07-31 9:24 ` steven at gcc dot gnu.org
2012-07-31 10:36 ` markus at trippelsdorf dot de [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-53880-4-qeLSKixdOx@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).