in the uClibc build system, we have some generic rules to quickly produce .E
(gcc -E) and .s (gcc -S) files for debugging purposes
normally this is fine as most of uClibc is simple .c files, but i wanted to
check out the final .s output of a .S that used a lot of macros
when i tried to use `gcc -S` though, the output was the same as using -E, and
the -o option was ignored
$ echo > test.c
$ gcc-4.1.0-beta20060120 -S test.c
$ file test.s
test.s: ASCII text
$ echo > test.S
$ gcc-4.1.0-beta20060120 -S test.S
# 1 "test.S"
# 1 "<built-in>"
# 1 "<command line>"
# 1 "test.S"
$ file test.s
test.s: cannot open `test.s' (No such file or directory)
--
Summary: using -S on a .S file does not work properly
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: pending
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: vapier at gentoo dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26016
