[Bug target/6077] [alpha-osf].s with -x assembler-with-cpp breaks mips-tfile

["tilps at hotmail dot com" <gcc-bugzilla at gcc dot gnu dot org>]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=6077


tilps@hotmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|3.2                         |3.4


------- Additional Comments From tilps@hotmail.com  2003-05-25 04:52 -------
an example with 3.4 from last month (in process of compiling a new one)

applied:~>g++ -x assembler-with-cpp blah.s --verbose
Reading specs from /home/gareth/lib/gcc-lib/alphaev56-dec-osf4.0d/3.4/specs
Configured with: ../gcc/configure --prefix=/home/gareth
--enable-version-specific-runtime-libs --with-stabs --enable-languages=c,c++,f77
Thread model: single
gcc version 3.4 20030413 (experimental)
 /home/gareth/lib/gcc-lib/alphaev56-dec-osf4.0d/3.4/cc1 -E -lang-asm -quiet -v
blah.s -o /tmp//ccZ9TsUi.s
ignoring nonexistent directory "/usr/local/include"
ignoring duplicate directory "/home/gareth/include"
ignoring nonexistent directory "/home/gareth/alphaev56-dec-osf4.0d/include"
#include "..." search starts here:
#include <...> search starts here:
 /home/gareth/include
 /home/gareth/lib/gcc-lib/alphaev56-dec-osf4.0d/3.4/include
 /usr/include
End of search list.
 as -g -nocpp -O0 -o /tmp//ccokiQ1v.o /tmp//ccZ9TsUi.s
 /home/gareth/lib/gcc-lib/alphaev56-dec-osf4.0d/3.4/mips-tfile -v -o
/tmp//ccokiQ1v.o blah.s
mips-tfile version 3.4 20030413 (experimental)
 /home/gareth/lib/gcc-lib/alphaev56-dec-osf4.0d/3.4/collect2 -G 8 -O1 -S
-call_shared /usr/lib/cmplrs/cc/crt0.o -L/home/gareth/lib -L/freeware/shlib
-L/home/gareth/lib/gcc-lib/alphaev56-dec-osf4.0d/3.4 -L/usr/lib/cmplrs/cc
-L/home/gareth/lib/gcc-lib/alphaev56-dec-osf4.0d/3.4/../../.. /tmp//ccokiQ1v.o
-lstdc++ -lm -lgcc_s -lgcc -lc -lgcc_s -lgcc

As can be seen - mips-tfile gets passed blah.s - not /tmp//ccZ9TsUi.s
In this case above - blah.s was a tempfile created from --save-temps of a simple
file - and so had no preprocessing instructions in it.  Therefore there is no
issues.  But the same thing occurs when blah.s Does contain preprocessing
directives.  (i just didnt have an assembly file handy with preprocessing
directives in it at this very second)



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.