https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90575
--- Comment #4 from Richard Biener ---
(In reply to Stephan Bergmann from comment #3)
> Or, to put it differently: It looks odd that while `gcc -gsplit-dwarf -c
> test.c -o /path/test.o` puts test.dwo next to test.o into /path/, `gcc
> -gsplit-d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90575
--- Comment #3 from Stephan Bergmann ---
Or, to put it differently: It looks odd that while `gcc -gsplit-dwarf -c
test.c -o /path/test.o` puts test.dwo next to test.o into /path/, `gcc
-gsplit-dwarf test.c -o /path/test` puts it into cwd.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90575
--- Comment #2 from Stephan Bergmann ---
(In reply to Richard Biener from comment #1)
> But that's how -gsplit-dwarf is designed.
Shouldn't it then be documented where any .dwo files are stored? At least in
combination with -o in comment 0, cwd
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90575
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
