https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71930
--- Comment #7 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #6)
> (In reply to Jonathan Wakely from comment #5)
> > But this is a dup of PR 67023 anyway.
> >
> > *** This bug has been marked as a duplicate of bug 67023 ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71930
--- Comment #6 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #5)
> But this is a dup of PR 67023 anyway.
>
> *** This bug has been marked as a duplicate of bug 67023 ***
Which I've pointed you to before:
https://gcc.gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71930
Jonathan Wakely changed:
What|Removed |Added
Resolution|INVALID |DUPLICATE
--- Comment #5 from Jonathan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71930
--- Comment #4 from Jeffrey Walton ---
(In reply to Jakub Jelinek from comment #3)
> (1) so what?
I suppose I should thank my lucky stars g++ did not invoke the preprocessor for
Fortran or Java then.
Maybe GCC could make it round robin so defin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71930
--- Comment #3 from Jakub Jelinek ---
(1) so what? The behavior for - input without -x is the same for all drivers.
gfortran -E - will not preprocess as if it is Fortran source, gcj -E - will not
preprocess as if it is a Java source (after all,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71930
--- Comment #2 from Jeffrey Walton ---
(In reply to Jakub Jelinek from comment #1)
> What makes you think that this is a bug?
I think its a bug (1) g++ is being used, and (2) -std=c++17 is being used. What
does a file extension have to do with a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71930
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
