public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* target/6115: mips-tfile errors out, dependent on filename order in command
@ 2002-03-31  4:56 tilps
  0 siblings, 0 replies; only message in thread
From: tilps @ 2002-03-31  4:56 UTC (permalink / raw)
  To: gcc-gnats


>Number:         6115
>Category:       target
>Synopsis:       mips-tfile errors out, dependent on filename order in command
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Mar 31 04:56:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Gareth Pearce
>Release:        3.2 20020318 (experimental)
>Organization:
>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
>Description:
in the configure script for gnu mp - conftes1.c and conftes2.s compiled togeather.  mips-tfile fails when the compile line contains the files in this order.  Reversing the filenames leads to success.  I feel that this is odd, and likely buggy.
------------------------------------------
conftes1.c
#ifdef __cplusplus
extern "C" { void underscore_test(); }
#endif
main () { underscore_test(); }
-------------------------------------------
conftes2.s
        .text
        .globl underscore_test
        underscore_test:
-------------------------------------------
>How-To-Repeat:
gcc conftes2.s conftes1.c works
gcc conftes1.c conftes2.s does not
>Fix:
workaround, ensure files are in other order.
>Release-Note:
>Audit-Trail:
>Unformatted:


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2002-03-31 12:56 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-03-31  4:56 target/6115: mips-tfile errors out, dependent on filename order in command tilps

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).