From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Richard Henderson <rth@twiddle.net>
Cc: <libc-alpha@sourceware.org>, <libc-ports@sourceware.org>,
Marcus Shawcroft <marcus.shawcroft@linaro.org>,
Richard Henderson <rth@redhat.com>,
David Holsgrove <david.holsgrove@xilinx.com>,
Chris Metcalf <cmetcalf@tilera.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: Implement fma in soft-fp
Date: Tue, 25 Jun 2013 16:13:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1306251603330.13034@digraph.polyomino.org.uk> (raw)
In-Reply-To: <51C9B79D.8070303@twiddle.net>
On Tue, 25 Jun 2013, Richard Henderson wrote:
> Of course, that would require glibc to build parts with the c++ compiler,
> so that may be a non-starter...
And libgcc, and the Linux kernel - I don't think requiring a C++ compiler
all over the place would be a good idea (and it would complicate
bootstrapping - you can't build libstdc++ without system headers, but need
to have built libgcc before building glibc, so a bootstrap compiler would
need the C++ compiler and a subset of the runtime libraries).
It's possible something could be done simply with inline always_inline
functions in C. The code doesn't just predate SRA, it predates inlining
on trees. I think I once discussed that issue, for this code, of why
inlines were less efficient than macros with GCC as it stood at that time,
with Peter Maydell around 1997/8.
(But maybe things like getting access to exception / rounding mode state,
which is in a local variable in the toplevel function, would complicate
any such macro-avoidance scheme, including the C++ ones.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2013-06-25 16:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-22 17:17 Joseph S. Myers
2013-06-25 15:30 ` Richard Henderson
2013-06-25 16:13 ` Joseph S. Myers [this message]
2013-06-25 16:23 ` Richard Henderson
2013-06-25 16:31 ` Richard Henderson
2013-06-25 16:45 ` Joseph S. Myers
2013-06-27 23:26 ` Joseph S. Myers
2013-07-02 12:57 ` Ping " Joseph S. Myers
2013-07-02 14:45 ` Richard Henderson
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=Pine.LNX.4.64.1306251603330.13034@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=cmetcalf@tilera.com \
--cc=davem@davemloft.net \
--cc=david.holsgrove@xilinx.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@sourceware.org \
--cc=marcus.shawcroft@linaro.org \
--cc=rth@redhat.com \
--cc=rth@twiddle.net \
/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).