From: Pavel Roskin <proski@gnu.org>
To: linux-sparse@vger.kernel.org
Subject: Re: [RFC PATCH] Handling multiple -include directives
Date: Fri, 22 Dec 2006 02:36:48 -0500 [thread overview]
Message-ID: <1166773008.21614.4.camel@dv> (raw)
In-Reply-To: <1166771189.18955.10.camel@dv>
On Fri, 2006-12-22 at 02:06 -0500, Pavel Roskin wrote:
> It seems to me that the existing add_pre_buffer() mechanism can be used
> instead. I'm just a bit worried why it wasn't done like this in the
> first place.
There was a reason to worry. Now create_builtin_stream() is run after
the includes have been processed, so that e.g. the Linux compiler.h
tells me that my compiler is too old (because it was included from the
command line before __GNUC__ was defined).
The initialization order needs some untangling. It's too intertwined
with the command line processing.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2006-12-22 7:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-22 7:06 [RFC PATCH] Handling multiple -include directives Pavel Roskin
2006-12-22 7:36 ` Pavel Roskin [this message]
2006-12-22 9:47 ` Christopher Li
2006-12-22 22:27 ` Pavel Roskin
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=1166773008.21614.4.camel@dv \
--to=proski@gnu.org \
--cc=linux-sparse@vger.kernel.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