From: "Joey Ye" <joey.ye@arm.com>
To: "'Ian Lance Taylor'" <iant@google.com>
Cc: "'gcc-patches'" <gcc-patches@gcc.gnu.org>
Subject: RE: [patch] Shorten Windows path
Date: Fri, 25 Apr 2014 10:28:00 -0000 [thread overview]
Message-ID: <002301cf606f$6a0d3300$3e279900$@arm.com> (raw)
In-Reply-To:
Ping
> -----Original Message-----
> From: Joey Ye [mailto:joey.ye@arm.com]
> Sent: Tuesday, April 01, 2014 6:18 PM
> To: 'Ian Lance Taylor'
> Cc: gcc-patches
> Subject: RE: [patch] Shorten Windows path
>
> Ian, thanks for your comments. Please find answers and new version below:
>
> > -----Original Message-----
> > From: Ian Lance Taylor [mailto:iant@google.com]
> > Sent: 25 March 2014 21:09
> > To: Joey Ye
> > Cc: gcc-patches
> > Subject: Re: [patch] Shorten Windows path
> >
> > On Tue, Mar 25, 2014 at 1:58 AM, Joey Ye <joey.ye@arm.com> wrote:
> > > Ping
> >
> > This code looks different on mainline.
> >
> > Writing "if ( do_canonical )" is not GCC style.
> Fixed
> >
> > This patch does not respect the configure option --disable-canonical-
> system-
> > headers.
> Solved by put is under the control of default
> ENABLE_CANONICAL_SYSTEM_HEADERS
> >
> > Also I personally don't actually know what the consequences would be.
> > Are there any downsides to canonicalizing header names?
> Since 4.8 system headers are by default canonicalized. This version only
> additionally canonical non-system headers. I can't think of any downsides.
>
> >
> > Ian
>
> ChangeLog.libcpp:
>
> * files.c (find_file_in_dir): Always try to shorten for DOS non-system
> headers.
> * init.c (ENABLE_CANONICAL_SYSTEM_HEADERS): Default enabled for DOS.
>
> diff --git a/libcpp/files.c b/libcpp/files.c
> index 7e88778..ad68682 100644
> --- a/libcpp/files.c
> +++ b/libcpp/files.c
> @@ -387,8 +387,14 @@ find_file_in_dir (cpp_reader *pfile, _cpp_file *file,
> bool *invalid_pch)
> char *copy;
> void **pp;
>
> - /* We try to canonicalize system headers. */
> - if (CPP_OPTION (pfile, canonical_system_headers) && file->dir->sysp)
> + /* We try to canonicalize system headers. For DOS based file
> + * system, we always try to shorten non-system headers, as DOS
> + * has a tighter constraint on max path length. */
> + if (CPP_OPTION (pfile, canonical_system_headers) && file->dir->sysp
> +#ifdef HAVE_DOS_BASED_FILE_SYSTEM
> + || !file->dir->sysp
> +#endif
> + )
> {
> char * canonical_path = maybe_shorter_path (path);
> if (canonical_path)
> diff --git a/libcpp/init.c b/libcpp/init.c
> index f10413a..b809515 100644
> --- a/libcpp/init.c
> +++ b/libcpp/init.c
> @@ -27,8 +27,12 @@ along with this program; see the file COPYING3. If not
> see
> #include "filenames.h"
>
> #ifndef ENABLE_CANONICAL_SYSTEM_HEADERS
> +#ifdef HAVE_DOS_BASED_FILE_SYSTEM
> +#define ENABLE_CANONICAL_SYSTEM_HEADERS 1
> +#else
> #define ENABLE_CANONICAL_SYSTEM_HEADERS 0
> #endif
> +#endif
>
> static void init_library (void);
> static void mark_named_operators (cpp_reader *, int);
next prev parent reply other threads:[~2014-04-25 10:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 9:06 Joey Ye
2014-03-25 13:18 ` Ian Lance Taylor
2014-04-01 10:17 ` Joey Ye
2014-06-04 18:45 ` Meador Inge
2014-04-25 10:28 ` Joey Ye [this message]
2014-04-25 13:58 ` Ian Lance Taylor
2014-05-09 6:30 ` Jeff Law
-- strict thread matches above, loose matches on Subject: below --
2014-02-19 7:45 Joey Ye
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='002301cf606f$6a0d3300$3e279900$@arm.com' \
--to=joey.ye@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@google.com \
/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).