http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55231
--- Comment #3 from Cary Coutant <ccoutant at gcc dot gnu.org> 2012-11-15 00:34:56 UTC --- (In reply to comment #1) > Another issue: > markus@x4 ~ % c++ -c -O0 -gsplit-dwarf test.ii -o /dev/null > /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.0/../../../../x86_64-pc-linux-gnu/bin/objcopy: > Warning: '/dev/null' is not an ordinary file I'm not sure what the right thing to do about this would be -- is there a portable way to check whether the -o option names a real filename or not? Is your intent that neither .o nor .dwo is generated? Why use -gsplit-dwarf in that case? I'm inclined to document this away. If you care, please clone this into a new bug report.
