From: Richard Henderson <rth@redhat.com>
To: gcc@gcc.gnu.org
Subject: Re: libgcc2 __fixsfdi
Date: Tue, 08 Oct 2002 11:48:00 -0000 [thread overview]
Message-ID: <20021008175920.GB2225@redhat.com> (raw)
In-Reply-To: <20021008171213.D979@bubble.sa.bigpond.net.au>
On Tue, Oct 08, 2002 at 05:12:13PM +0930, Alan Modra wrote:
> Yes, and that's probably the strongest argument I have for float
> -> int conversions to peg at signed max/min. If float -> unsigned
> peg at unsigned max, then it why not something similar for signed
> conversions?
I dunno. I'm of two minds here. On the one hand, pegging at
particular values makes mathematic sense. On the other,
overflow is undefined (at least in C, C++, and Fortran), so
there's little point spending any energy on it. You're
increasing the code size in libgcc for no apparent gain.
Anyone else out there have an opinion?
> Also, a reminder that neither your or my fix to __floatdisf has
> been applied yet..
Oh, right. Let's go with yours for now, since it uses fewer
operations.
r~
prev parent reply other threads:[~2002-10-08 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 8:11 Alan Modra
2002-10-04 12:45 ` Richard Henderson
2002-10-08 1:46 ` Alan Modra
2002-10-08 11:48 ` Richard Henderson [this message]
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=20021008175920.GB2225@redhat.com \
--to=rth@redhat.com \
--cc=gcc@gcc.gnu.org \
/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).