This is the mail archive of the gcc-patches@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: [Patch, Fortran, committed] Add LANG=C to libgfortran/mk-kinds-h.sh

From: Tobias Schlüter <tobias dot schlueter at physik dot uni-muenchen dot de>
To: Tobias Burnus <burnus at net-b dot de>
Cc: gcc-patches <gcc-patches at gcc dot gnu dot org>, "'fortran at gcc dot gnu dot org'" <fortran at gcc dot gnu dot org>
Date: Fri, 26 Oct 2007 21:15:06 +0200
Subject: Re: [Patch, Fortran, committed] Add LANG=C to libgfortran/mk-kinds-h.sh
References: <472239EC.3070309@net-b.de>

Tobias Burnus wrote:

After getting failures when building GCC with a non-English locale, I
found out that

    huge=`$compile -c -fdump-parse-tree tmq$$.f90 | grep TRANSFER \
                | sed 's/ *TRANSFER *// ; s/_.*//'`

only works if TRANSFER is not translated in the dump.

I committed attached patch as obvious. (As the change to mk-kinds-h.sh
is brand new, only today's GCC trunk was affected.)

Since I couldn't find this expression, and since I can't think of an occasion where one would both want to match TRANSFER and where it's a good idea to translate it, I'm curious: could you say where or how this happens?

Cheers,
- Tobi

Follow-Ups:
- Re: [Patch, Fortran, committed] Add LANG=C to libgfortran/mk-kinds-h.sh
  - From: Tobias Burnus

References:
- [Patch, Fortran, committed] Add LANG=C to libgfortran/mk-kinds-h.sh
  - From: Tobias Burnus

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