This is the mail archive of the
mailing list for the GCC project.
Re: [patch c/c++]: Unify behavior for native/cross include
- From: Richard Guenther <richard dot guenther at gmail dot com>
- To: Kai Tietz <ktietz70 at googlemail dot com>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>, "Joseph S. Myers" <joseph at codesourcery dot com>, Richard Henderson <rth at redhat dot com>
- Date: Wed, 28 Jul 2010 14:13:13 +0200
- Subject: Re: [patch c/c++]: Unify behavior for native/cross include
- References: <AANLkTinaVrx78KVVXDbUsxkCRawUVpEwFKVXhg6BjdDO@mail.gmail.com>
On Wed, Jul 28, 2010 at 1:52 PM, Kai Tietz <firstname.lastname@example.org> wrote:
> this patch tries to unify behavior of native- vs. cross-toolchains.
> Issue is that the order of the include folders differ (without good
> reason) for those. For native the 'local_include_dir' comes before the
> 'gcc-internal headers', but for cross the 'gcc-internal headers' are
> coming before any other headers. This all makes it pretty hard to
> predict for targets like 'mingw', where the some headers (float.h is
> here such a case) have to be forwarded by include_next from
> target-headers, or by gcc's internal headers.
> By this cause I suggest the following order in general to be used by gcc
> The fixed-include should come before the standard_include_dir, as
> those shall be handled by fixed-include. The gcc-internal should be
> the first of the C headers and first after the g++-header part.
> 2010-07-28 ?Kai Tietz
> ? ? ? ?* cppdefault.c (cpp_include_defaults): Move GCC_INCLUDE_DIR before
> ? ? ? ?LOCAL_INCLUDE_DIR and move FIXED_INCLUDE_DIR before
> I tested this for x86_64-w64-mingw32 and for i686-w64-mingw32. Ok for apply?
Re-ordering CROSS_INCLUDE_DIR, TOOL_INCLUDE_DIR and
SYSTEM_INCLUDE_DIR before FIXED_INCLUDE_DIR is unrelated
to your problem at hand, right? I see no reason why those couldn't
> |? (\_/) This is Bunny. Copy and paste
> | (='.'=) Bunny into your signature to help
> | (")_(") him gain world domination