This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PR libfortran/62768] Handle filenames with embedded nulls
- From: "N.M. Maclaren" <nmm1 at cam dot ac dot uk>
- To: Janne Blomqvist <blomqvist dot janne at gmail dot com>
- Cc: Hans-Peter Nilsson <hp at bitrange dot com>, FX <fxcoudert at gmail dot com>, Fortran List <fortran at gcc dot gnu dot org>, GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: 18 Sep 2014 10:04:50 +0100
- Subject: Re: [PR libfortran/62768] Handle filenames with embedded nulls
- Authentication-results: sourceware.org; auth=none
- References: <CAO9iq9E75dJ2AEMfnB_Ro68FBEpYz=BjS2-fxqWNUznbCtpH+Q at mail dot gmail dot com> <CAO9iq9GP7x_sYFAzRYZryw8LEJxSBY_nrXcHHQG+BQPGJTFcZQ at mail dot gmail dot com> <F7035948-4928-4A65-90DF-1B12D7316FEB at gmail dot com> <CAO9iq9EENvbr-BSEOPZeV9325xn8=GX02z8y46_6cvHvL9-weg at mail dot gmail dot com> <alpine dot BSF dot 2 dot 02 dot 1409170720140 dot 97960 at arjuna dot pair dot com> <CAO9iq9H2ApQJP-k0a3A-MOGGqPvaGNd1UMhBy2NahfUTGnKNqw at mail dot gmail dot com> <alpine dot BSF dot 2 dot 02 dot 1409171203330 dot 89896 at arjuna dot pair dot com> <alpine dot BSF dot 2 dot 02 dot 1409171424450 dot 96402 at arjuna dot pair dot com> <alpine dot BSF dot 2 dot 02 dot 1409171634100 dot 96402 at arjuna dot pair dot com> <CAO9iq9GRf9z3538RbDxv6_E5gcC7JC08kBynpYSf3mbfauYfrQ at mail dot gmail dot com> <alpine dot BSF dot 2 dot 02 dot 1409171753590 dot 96402 at arjuna dot pair dot com> <CAO9iq9Ez0-vrHsBhy-YHmLQ6KmwNmxAqgAtLOZS_3-soCsOZoQ at mail dot gmail dot com> <alpine dot BSF dot 2 dot 02 dot 1409172151260 dot 83306 at arjuna dot pair dot com> <alpine dot BSF dot 2 dot 02 dot 1409180401530 dot 54493 at arjuna dot pair dot com> <CAO9iq9FPrhaXvcoGeY4cXmCEspLVAD93_OnV+=cP4f7do4RjjA at mail dot gmail dot com>
On Sep 18 2014, Janne Blomqvist wrote:
Apparently libgfortran is not compiled with -Werror, at least
not for crosses. Maybe -Werror is there for native but I'm not
sure as I see some "warning: array subscript has type 'char'
[-Wchar-subscripts]" which seems generic and also some others.
Though no more than can be fixed or excepted, IMHO.
No, Werror isn't used. It was tried, but apparently caused issues.
From the changelog:
2008-06-13 Tobias Burnus <burnus@net-b.de>
* configure.ac (AM_CFLAGS): Remove -Werror again.
I have a vague recollection that there were issues with system headers
on non-glibc targets. It would be nice if Werror was used by default,
I think we've had a few cases where bugs have slipped past due to it.
I wasn't involved, but that sounds more than just likely! I have had
that experience with several options, including Werror, pedantic and
specific standards ones. My experience is that most vendors clean up
at least the standard C headers with time, and usually the more basic
POSIX ones, but any others often remain beyond redemption.
And what is not going to help is the ongoing incompatibilities
in de jure and de facto standards. I have certainly seen standard
headers that would compile only with specific language selection
options. Oh, yes, their COMPILER supported other ones - you just
couldn't use some important system headers with them :-(
If I get time, I will look at the libfortran header use and see if I
can make any useful specific comments.
Regards,
Nick Maclaren.