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

On Wed, 2007-07-25 at 07:17 -0400, Daniel Jacobowitz wrote:

> > 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).

OK, so let's ignore the doc change I proposed.  Is the patch to
eliminate the warning going about it the right way?

Cheers, Ben

  reply	other threads:[~2007-07-25 22:57 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
2007-07-25 23:11   ` Ben Elliston [this message]
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=1185404270.6119.2.camel@localhost \
    --to=bje@au1.ibm.com \
    --cc=drow@false.org \
    --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).