From: Joe Buck <jbuck@synopsys.com>
To: wilson@cygnus.com (Jim Wilson)
Cc: ben@proximity.com.au, egcs@cygnus.com, hjl@lucon.org
Subject: Re: Building a cross compiler
Date: Wed, 29 Apr 1998 08:38:00 -0000 [thread overview]
Message-ID: <199804291538.IAA19301@atrus.synopsys.com> (raw)
In-Reply-To: <199804290045.RAA24450@rtl.cygnus.com>
> I think this should be fixed by rewriting the x86 port to implement libgcc1
> as an assembler file instead of the perform_* macros, and then we should
> eliminate the perform_* macros so that no one else will be tempted to use
> them. This is how all other ports work nowadays.
Perhaps I'm missing something, but wouldn't that mean that the
assembler functions would no longer be inline?
next prev parent reply other threads:[~1998-04-29 8:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-26 18:12 The Red Fox
1998-04-27 0:33 ` ralf
1998-04-27 11:10 ` H.J. Lu
1998-04-27 11:10 ` ralf
1998-04-27 11:10 ` H.J. Lu
1998-04-28 19:49 ` Todd Vierling
1998-04-27 14:44 ` Ian Lance Taylor
1998-04-28 19:49 ` Jim Wilson
1998-04-29 8:38 ` Joe Buck [this message]
1998-04-29 14:48 ` Jim Wilson
1998-05-04 21:55 ` Jeffrey A Law
1998-05-05 23:29 ` The Red Fox
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=199804291538.IAA19301@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=ben@proximity.com.au \
--cc=egcs@cygnus.com \
--cc=hjl@lucon.org \
--cc=wilson@cygnus.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).