This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: RFC: case insensitive for #include

From: Chris Lattner <clattner at apple dot com>
To: H.J. Lu <hjl dot tools at gmail dot com>
Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>, "Ye, Joey" <joey dot ye at intel dot com>, "Guo, Xuepeng" <xuepeng dot guo at intel dot com>
Date: Wed, 28 Jan 2009 12:21:29 -0800
Subject: Re: RFC: case insensitive for #include
References: <6dc9ffc80901281151g72a34e5clb64893a2aaf798b1@mail.gmail.com>

On Jan 28, 2009, at 11:51 AM, H.J. Lu wrote:

Hi,
I got a request to try "FOO.H" if foo.h doesn't exist when dealing
with
#include "foo.h"

Any comments?

I strongly recommend against this, unless this is only a "last chance" fall back.

From a performance standpoint, if you have -Idir1 -Idir2 -Idir3, you don't want to stat all variants of "foo.h" in dir1 before moving on to dir2. If you do a full search for foo.h in all appropriate search paths, and then redo it only on failure, then the performance issue goes away. However, in that case you get very difficult to explain behavior if you have multiple files with spelling variants of foo.h in different search paths.

-Chris

Follow-Ups:
- Re: RFC: case insensitive for #include
  - From: H.J. Lu

References:
- RFC: case insensitive for #include
  - From: H.J. Lu

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]