target/6077: .s with -x assembler-with-cpp breaks mips-tfile

[gareth at Physics dot usyd dot edu dot au]

>Number:         6077
>Category:       target
>Synopsis:       .s with -x assembler-with-cpp breaks mips-tfile
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Mar 27 19:36:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Gareth Pearce
>Release:        3.2 20020318 (experimental)
>Organization:
none
>Environment:
System: OSF1 applied.physics.usyd.edu.au V4.0 878 alpha
Machine: alpha
host: alphaev56-dec-osf4.0d
build: alphaev56-dec-osf4.0d
target: alphaev56-dec-osf4.0d
configured with: ../gcc/configure --prefix=/home/gareth --enable-threads
>Description:
	-x assembler-with-cpp does not cause the filename extension to 
change internally, therefore the spec files fail to deal with .s files 
as if they were .S - this is specifically a problem with systems using 
mips-tfile.  In this case mips-tfile gets passed the original .s 
filename instead of the temporary output from cpp0, this causes 
mipstfile to fail if the input .s file contains preprocessor stuff.
	I am sure that similar problems could be had with other 
combinations of -x options, but this one in particular causes problems 
for me.
>How-To-Repeat:
	Compile any assembly file with cpp information which ends in .s 
using -x assembler-with-cpp, on a target which uses mips-tfile 
>Fix:
	Workaround is to use .S for assembly files with cpp, but -x 
assembler-with-cpp should really work I think.
	Possible solutions: 
	1. make -x options change the filename passed to the spec file
processing system.
	2. allow -x options to be checked in spec files and add a stack 
of conditionals to the current spec file definitions for each platform.
>Release-Note:
>Audit-Trail:
>Unformatted: