--
jsm28 at gcc dot gnu dot org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirm
--- Comment #8 from neil at daikokuya dot co dot uk 2006-05-24 12:55
---
Subject: Re: New: bogus 'backslash-newline at end of file' warning
sabre at nondot dot org wrote:-
> $ gcc bug.c -Wall -pedantic -fsyntax-only -trigraphs -std=c99
>
> yields:
> bug.c:2:9: warning: trigraph ??/
--- Comment #7 from pinskia at gcc dot gnu dot org 2006-05-24 06:42 ---
it is not really an extension in the normal way. Since the standard says this
is undefined behavior at compile time, we can do different things in different
situtations dealing with no return at the end of the file.
--- Comment #6 from sabre at nondot dot org 2006-05-24 06:36 ---
> It is not really an extension, just undefined at compile time which
> isdiffferent than supporting.
It's marked as a pedwarn. That's a pretty clear demonstration that this is a
feature, and that it's a known extension.
--- Comment #5 from pinskia at gcc dot gnu dot org 2006-05-24 06:33 ---
(In reply to comment #4)
> > This might be why it is undefined at compile time if the file does not end
> > in a
> > new-line or not :).
>
> However, GCC *does* supports this as an extension, hence the expected ped
--- Comment #4 from sabre at nondot dot org 2006-05-24 06:26 ---
> This might be why it is undefined at compile time if the file does not end in
> a
> new-line or not :).
However, GCC *does* supports this as an extension, hence the expected pedwarn.
> I don't think that warning is tha
--- Comment #3 from pinskia at gcc dot gnu dot org 2006-05-24 06:25 ---
bug.c:2:9: warning: backslash-newline at end of file
I don't think that warning is that bogus. It is true too. Maybe misleading.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27750
--- Comment #2 from pinskia at gcc dot gnu dot org 2006-05-24 06:23 ---
This might be why it is undefined at compile time if the file does not end in a
new-line or not :).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27750
--- Comment #1 from sabre at nondot dot org 2006-05-24 06:21 ---
I guess I should have been more specific. Instead of "backslash-newline at end
of file", I'd expect to get "no newline at end of file", which is also missing.
-Chris
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=277
