public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug middle-end/114667] New: `gcc -O2 t.c -fdump-tree-optimized=/dev/stdout -fdump-tree-all` produces `error: could not open dump file`
@ 2024-04-09 21:08 pinskia at gcc dot gnu.org
0 siblings, 0 replies; only message in thread
From: pinskia at gcc dot gnu.org @ 2024-04-09 21:08 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114667
Bug ID: 114667
Summary: `gcc -O2 t.c -fdump-tree-optimized=/dev/stdout
-fdump-tree-all` produces `error: could not open dump
file`
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: diagnostic, rejects-valid
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: pinskia at gcc dot gnu.org
Target Milestone: ---
```
[apinski@xeond2 gcc]$ ~/upstream-gcc/bin/gcc -O2 -S
-fdump-tree-optimized=/dev/stdout -fdump-tree-all t.c
t.c: In function ‘main’:
t.c:5:5: error: could not open dump file ‘/usr/local/include’: Is a directory
5 | int main()
| ^~~~
```
This has been failing this way since at least 9.1.0 .
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2024-04-09 21:08 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-04-09 21:08 [Bug middle-end/114667] New: `gcc -O2 t.c -fdump-tree-optimized=/dev/stdout -fdump-tree-all` produces `error: could not open dump file` pinskia at gcc dot gnu.org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).