From: Ralf Baechle <ralf@oss.sgi.com>
To: Jeff Harrell <jharrell@ti.com>
Cc: linux@cthulhu.engr.sgi.com, bbrown@ti.com
Subject: Re: C/Assembler listing files
Date: Tue, 4 Jan 2000 02:43:53 +0100 [thread overview]
Message-ID: <20000104024353.B6063@uni-koblenz.de> (raw)
In-Reply-To: <38712453.B0BCE0CD@ti.com>
On Mon, Jan 03, 2000 at 03:36:03PM -0700, Jeff Harrell wrote:
> Has anyone tried to generate an interleaved C and Assembler listing file
> with the MIPS cross compilation tools? I tried to pass the following flags
> to gcc
> (and the assembler):
I just tried this on my current version of the x-tools and it seemed
to work. There is a number of other problems, mostly that 32-bit
static linking of PIC code is broken and then infinite 64-bit problems
which prevent me from making a real release and declaring them to be
``the'' official versions. If that doesn't bother you, go ahead and
get the stuff from oss.sgi.com:/pub/linux/mips/crossdev/testing/.
Ralf
prev parent reply other threads:[~2000-01-04 1:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-03 22:36 C/Assembler listing files Jeff Harrell
2000-01-04 1:43 ` Ralf Baechle [this message]
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=20000104024353.B6063@uni-koblenz.de \
--to=ralf@oss.sgi.com \
--cc=bbrown@ti.com \
--cc=jharrell@ti.com \
--cc=linux@cthulhu.engr.sgi.com \
/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