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:44:00 -0000	[thread overview]
Message-ID: <bug-55399-4-3iozHninql@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 #5 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2012-11-20 00:44:06 UTC ---
So you need to trace the cause of not using the header.  -Winvalid-pch may 
help, but ultimately you need to find whether the file is examined at all, 
if not then why not, and if examined but rejected then what the cause of 
the rejection is.  And compare with working systems.


  parent reply	other threads:[~2012-11-20  0:44 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
2012-11-20  0:32 ` sje at gcc dot gnu.org
2012-11-20  0:44 ` joseph at codesourcery dot com [this message]
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-3iozHninql@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).