public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/37033] [4.4 Regression] Revision 138733 breaks PCH
Date: Sun, 10 Aug 2008 07:29:00 -0000 [thread overview]
Message-ID: <20080810072825.392.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37033-682@http.gcc.gnu.org/bugzilla/>
------- Comment #6 from pinskia at gcc dot gnu dot org 2008-08-10 07:28 -------
>It doesn't work on gcc.dg/pch/valid-1b.c since it explicitly tests -g vs -g0:
I don't think valid-1b.c is valid any more in general, You have to supply -g
to get a valid PCH now that works with -g.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37033
next prev parent reply other threads:[~2008-08-10 7:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 22:42 [Bug debug/37033] New: " hjl dot tools at gmail dot com
2008-08-07 19:00 ` [Bug debug/37033] " hjl dot tools at gmail dot com
2008-08-07 19:11 ` hjl dot tools at gmail dot com
2008-08-07 20:09 ` rth at gcc dot gnu dot org
2008-08-07 20:12 ` rth at gcc dot gnu dot org
2008-08-09 15:16 ` hjl dot tools at gmail dot com
2008-08-10 7:29 ` pinskia at gcc dot gnu dot org [this message]
2008-08-10 16:58 ` hjl dot tools at gmail dot com
2008-08-11 0:24 ` pinskia at gcc dot gnu dot org
2008-08-22 15:16 ` [Bug debug/37033] [4.4 Regression] Revision 138733 breaks -g vs -g0 for PCH rguenth at gcc dot gnu dot org
2008-09-09 21:26 ` janis at gcc dot gnu dot org
2008-11-17 12:28 ` [Bug target/37033] " ubizjak at gmail dot com
2008-11-28 7:36 ` geoffk at gcc dot gnu dot org
2008-12-05 6:58 ` aoliva at gcc dot gnu dot org
2008-12-10 17:34 ` aoliva at gcc dot gnu dot org
2008-12-10 17:40 ` aoliva at gcc dot gnu dot 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=20080810072825.392.qmail@sourceware.org \
--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).