public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Ben Elliston <bje@au1.ibm.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: PATCH: eliminate warnings from c-opts.c
Date: Wed, 25 Jul 2007 11:21:00 -0000	[thread overview]
Message-ID: <20070725111716.GA7240@caradoc.them.org> (raw)
In-Reply-To: <1185053238.32204.12.camel@localhost>

On Sun, Jul 22, 2007 at 07:27:18AM +1000, Ben Elliston wrote:
> While I was at it, I found the internals manual contained a FIXME
> comment about the tm_p.h header that doesn't seem right to me:
> 
>   FIXME: why is such a separate header necessary?
> 
> Unless I'm mistaken, it is done this way so that GCC sources can include
> an independently named "tm_p.h" without needing to know the name of the
> <machine>-protos.h header.  However, this seems too obvious, so I
> suspect I'm wrong.  :-)

I think the question is relative to tm.h (and it has something to do
with which files include one and not the other).

-- 
Daniel Jacobowitz
CodeSourcery

  reply	other threads:[~2007-07-25 11:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-21 23:36 Ben Elliston
2007-07-25 11:21 ` Daniel Jacobowitz [this message]
2007-07-25 23:11   ` Ben Elliston
2007-07-26 20:51   ` Kaveh R. GHAZI

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=20070725111716.GA7240@caradoc.them.org \
    --to=drow@false.org \
    --cc=bje@au1.ibm.com \
    --cc=gcc-patches@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).