From: Jeffrey A Law <law@cygnus.com>
To: Joel Sherrill <joel@OARcorp.com>
Cc: egcs@cygnus.com
Subject: Re: REGISTER_PREFIX in egcs 1.0.2
Date: Sun, 03 May 1998 22:02:00 -0000 [thread overview]
Message-ID: <23594.894252199@hurl.cygnus.com> (raw)
In-Reply-To: <Pine.BSF.3.96.980502104403.8122D-100000@vespucci.advicom.net>
In message < Pine.BSF.3.96.980502104403.8122D-100000@vespucci.advicom.net >you write:
> The RTEMS source code uses the same trick as newlib to write portable
> assembly language across object formats. We try to use the macros
> __REGISTER_PREFIX__ and __USER_LABEL_PREFIX__ which are sometimes provided
> by gcc. This works great on the m68k and a handful of other CPU families.
> But it is not supported by all.
>
> This would be easy to add to all the configurations if one had the right
> knowledge. How would be the safest way to go about adding these to make
> sure they are correct?
I'm not 100% sure I understand what you're asking for.
Are you asking for all the ports to actually use REGISTER_PREFIX
and friends? This would be a lot of work, and I doubt it's worth
the effort since few ports need this facility.
Or are you asking that REGISTER_PREFIX and friends always be available
for use by assembly code fed through gcc/cpp? It looks like we try
to always make them available (defaulting their value to "" if the
target doesn't provide a definition).
jeff
next prev parent reply other threads:[~1998-05-03 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-05-02 8:47 Joel Sherrill
1998-05-03 22:02 ` Jeffrey A Law [this message]
1998-05-04 5:51 ` Joel Sherrill
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=23594.894252199@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=joel@OARcorp.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).