From: Nick Clifton <nickc@cambridge.redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: Multilib support in gdb.asm tests
Date: Fri, 11 Jan 2002 09:28:00 -0000 [thread overview]
Message-ID: <m3bsg06buq.fsf@north-pole.nickc.cambridge.redhat.com> (raw)
In-Reply-To: <3C3F05DE.8010007@cygnus.com>
Hi Andrew,
> > + # FIXME: Invoking the assembler directly is incorrect.
>
>
> Just FYI, this is wrong. These tests apply to targets that do not
> have a C compiler so must be able to invoke the assembler directly.
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.
Cheers
Nick
next prev parent reply other threads:[~2002-01-11 17:28 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 [this message]
2002-01-12 5:47 ` Mark Kettenis
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=m3bsg06buq.fsf@north-pole.nickc.cambridge.redhat.com \
--to=nickc@cambridge.redhat.com \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.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