[Bug c/92720] cc1 accepts #include /dev/stdin inline

2019-11-30 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92720 --- Comment #9 from Jonathan Wakely --- (In reply to Dennis Clarke from comment #7) > Sort of a vague idea there. Whatever "can be" means. However the file > /dev/stdin really is neither a "header" nor is it a "source" file. It could be. `echo

[Bug c/92720] cc1 accepts #include /dev/stdin inline

2019-11-30 Thread dclarke at blastwave dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92720 --- Comment #8 from Dennis Clarke --- (In reply to jos...@codesourcery.com from comment #6) . . . > In turn, that section "Include Operation" has more details. It doesn't > mention includes with an absolute path, but I think that's because the

[Bug c/92720] cc1 accepts #include /dev/stdin inline

2019-11-30 Thread dclarke at blastwave dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92720 --- Comment #7 from Dennis Clarke --- Looking at the document n1256 "ISO/IEC 9899:TC3 WG14/N125" ye C99 specifications we see section 6.10.2 Source file inclusion subsection 1 which almost seems clear : A #include directive shall identify

[Bug c/92720] cc1 accepts #include /dev/stdin inline

2019-11-30 Thread joseph at codesourcery dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92720 --- Comment #6 from joseph at codesourcery dot com --- For the documentation of implementation-defined preprocessor behavior (as required to be documented by a C implementation for anything the C standard says is implementation-defined; in

[Bug c/92720] cc1 accepts #include /dev/stdin inline

2019-11-30 Thread dclarke at blastwave dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92720 --- Comment #5 from Dennis Clarke --- Glad someone looked at this. I was going to try again with LLVM/Clang and then a few other places on a few other architectures. Why bother? However if this is "implementation defined" then we should see a

[Bug c/92720] cc1 accepts #include /dev/stdin inline

2019-11-29 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92720 --- Comment #4 from Jonathan Wakely --- (In reply to Jonathan Wakely from comment #2) > (In reply to Dennis Clarke from comment #0) > > This may require a bit of a dive into the specifications however > > an inline include of /dev/stdin seems

[Bug c/92720] cc1 accepts #include /dev/stdin inline

2019-11-29 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92720 --- Comment #2 from Jonathan Wakely --- (In reply to Dennis Clarke from comment #0) > This may require a bit of a dive into the specifications however > an inline include of /dev/stdin seems wrong for some definition > of wrong. There's no

[Bug c/92720] cc1 accepts #include /dev/stdin inline

2019-11-29 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92720 --- Comment #3 from Jonathan Wakely --- (In reply to Andrew Pinski from comment #1) > GCC does not check the files. > > >echo '\042hello botfelk\\n\042' > This one fails for me too: > In file included from t8.c:5:0: > /dev/stdin: In function

[Bug c/92720] cc1 accepts #include /dev/stdin inline

2019-11-28 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92720 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---