public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug pch/55399] pch tests fail on mips-mti-linux-gnu target
Date: Tue, 20 Nov 2012 00:16:00 -0000	[thread overview]
Message-ID: <bug-55399-4-r2xj4KqNkl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55399-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #3 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2012-11-20 00:15:42 UTC ---
Well, you need to start by looking at how it "fails", e.g. segfault, 
macros found to be predefined not the same as those predefined when the 
PCH was created, other test for when PCH file can be included failing.  
And then track things from there.  If stdc-predef.h is in your glibc 
sources, it should also have been installed in the usr/include directory 
of your glibc installation, and the point at which state is saved should 
be the point after stdc-predef.h is included (so its macros are considered 
predefined, and so that PCH files can be included after the implicit 
stdc-predef.h include without failing the test for consistency of 
predefined macros).


  parent reply	other threads:[~2012-11-20  0:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-19 21:36 [Bug pch/55399] New: " sje at gcc dot gnu.org
2012-11-19 22:55 ` [Bug pch/55399] " joseph at codesourcery dot com
2012-11-19 23:53 ` sje at gcc dot gnu.org
2012-11-20  0:16 ` joseph at codesourcery dot com [this message]
2012-11-20  0:32 ` sje at gcc dot gnu.org
2012-11-20  0:44 ` joseph at codesourcery dot com
2012-11-21 21:29 ` sje at gcc dot gnu.org
2012-11-21 21:42 ` sje at gcc dot gnu.org
2015-06-12 11:59 ` jakub 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-55399-4-r2xj4KqNkl@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).