From: Noah Lavine <noah.b.lavine@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>,
Andreas Schwab <schwab@linux-m68k.org>,
Emacs development discussions <Emacs-devel@gnu.org>
Subject: Re: (0 <= i && i < N) is not "backwards"
Date: Mon, 25 Mar 2013 11:28:11 -0400 [thread overview]
Message-ID: <CA+U71=Nm3qwwdjgaJW7C0c9zpGb2b-3s=0_eqhfhF1AhHo=-4w@mail.gmail.com> (raw)
In-Reply-To: <83mwtr1pow.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 802 bytes --]
On Mon, Mar 25, 2013 at 11:09 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Noah Lavine <noah.b.lavine@gmail.com>
> > Date: Mon, 25 Mar 2013 10:58:28 -0400
> > Cc: Paul Eggert <eggert@cs.ucla.edu>, Andreas Schwab <
> schwab@linux-m68k.org>,
> > Emacs development discussions <Emacs-devel@gnu.org>
> >
> > To continue a tangent, if adding an explicit isnan() makes the code run
> any
> > slower, I think you should file a bug with GCC to get that fixed.
>
> I don't think GCC is a problem: isnan is a builtin function there, so
> even a function call overhead is spared.
>
>
Oh, that's good. I didn't know how it was implemented.
I mean that GCC should be able to convert ((x > 0) || isnan(x)) to !(x <=
0) if the second expression is actually faster. It seems like a fairly
simple rewrite.
[-- Attachment #2: Type: text/html, Size: 1398 bytes --]
next prev parent reply other threads:[~2013-03-25 15:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-24 23:14 (0 <= i && i < N) is not "backwards" Paul Eggert
2013-03-24 23:53 ` Pascal J. Bourguignon
2013-03-25 14:23 ` Stefan Monnier
2013-03-25 14:59 ` Andreas Schwab
2013-03-25 8:20 ` Eli Zaretskii
2013-03-25 14:35 ` Paul Eggert
2013-03-25 14:53 ` Eli Zaretskii
2013-03-25 14:58 ` Noah Lavine
2013-03-25 15:09 ` Eli Zaretskii
2013-03-25 15:28 ` Noah Lavine [this message]
2013-03-25 16:49 ` Paul Eggert
2013-03-25 16:59 ` Eli Zaretskii
2013-03-30 21:45 ` Jim Meyering
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='CA+U71=Nm3qwwdjgaJW7C0c9zpGb2b-3s=0_eqhfhF1AhHo=-4w@mail.gmail.com' \
--to=noah.b.lavine@gmail.com \
--cc=Emacs-devel@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=schwab@linux-m68k.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.