public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tilps@hotmail.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/6077] [alpha-osf].s with -x assembler-with-cpp breaks mips-tfile
Date: Sun, 25 May 2003 05:02:00 -0000 [thread overview]
Message-ID: <20030525045251.10677.qmail@sources.redhat.com> (raw)
In-Reply-To: <20020327193600.6077.tilps@hotmail.com>
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.
next parent reply other threads:[~2003-05-25 4:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020327193600.6077.tilps@hotmail.com>
2003-05-25 5:02 ` tilps@hotmail.com [this message]
2003-08-10 23:00 ` pinskia at gcc dot gnu dot org
2004-12-28 5:04 ` pinskia at gcc dot gnu dot org
2005-01-07 1:05 ` cvs-commit at gcc dot gnu dot org
2005-01-07 1:35 ` pinskia at gcc dot gnu dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030525045251.10677.qmail@sources.redhat.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).