From: Mark Kettenis <kettenis@science.uva.nl>
To: Nick Clifton <nickc@cambridge.redhat.com>
Cc: Andrew Cagney <ac131313@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: RFA: Multilib support in gdb.asm tests
Date: Sat, 12 Jan 2002 05:47:00 -0000 [thread overview]
Message-ID: <s3iwuyn1y2z.fsf@soliton.wins.uva.nl> (raw)
In-Reply-To: Nick Clifton's message of 11 Jan 2002 17:23:09 +0000
Nick Clifton <nickc@cambridge.redhat.com> writes:
> How about this alternative wording of the comment:
>
> # WARNING: Invoking the assembler directly is problematic.
> # For targets which support multilibs a compile time switch is used
> # to select the appropriate multilibs. This switch may not be same
> # as the switch that the compiler will pass on to the assembler. For
> # example if big-endian and little-endian multilibs are supported
> # the compiler options will probably be -mbig-endian and -mlittle-endian
> # but, for historical reasons, the assembler options are probably -EB
> # and -EL.
> #
> # Since these tests are supposed to be able to be run for targets for
> # which there is no compiler we cannot just invoke a compiler driver
> # program (eg 'gcc') to handle this translation for us. For now we
> # just hard code the endian translation and hope that there are no
> # others that are needed.
I'm a bit puzzled by this comment. These tests already invoke `gcc'
for doing the final link. Isn't that a problem too?
As an aside, using gcc for the final link is causing problems on
FreeBSD too.
Mark
next prev parent reply other threads:[~2002-01-12 13:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-11 4:08 Nick Clifton
2002-01-11 7:33 ` Andrew Cagney
2002-01-11 7:42 ` Andrew Cagney
2002-01-11 9:22 ` Nick Clifton
2002-01-11 9:50 ` Andrew Cagney
2002-01-20 16:19 ` Andrew Cagney
2002-01-11 9:28 ` Nick Clifton
2002-01-12 5:47 ` Mark Kettenis [this message]
2002-01-12 10:01 ` Michael Snyder
2002-01-13 0:14 ` Nick Clifton
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=s3iwuyn1y2z.fsf@soliton.wins.uva.nl \
--to=kettenis@science.uva.nl \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=nickc@cambridge.redhat.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