public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Ondřej Bílka" <neleai@seznam.cz>
To: "marc.glisse at normalesup dot org" <sourceware-bugzilla@sourceware.org>
Cc: glibc-bugs@sourceware.org
Subject: Re: [Bug math/15384] New: One constant fewer in ieee754/dbl-64/wordsize-64/s_finite.c
Date: Sun, 21 Apr 2013 10:54:00 -0000	[thread overview]
Message-ID: <20130421103937.GA9642@domone.kolej.mff.cuni.cz> (raw)
In-Reply-To: <bug-15384-131@http.sourceware.org/bugzilla/>

On Sun, Apr 21, 2013 at 10:06:00AM +0000, marc.glisse at normalesup dot org wrote:
> http://sourceware.org/bugzilla/show_bug.cgi?id=15384
> 
>              Bug #: 15384
>            Summary: One constant fewer in
>                     ieee754/dbl-64/wordsize-64/s_finite.c
>            Product: glibc
>            Version: unspecified
>             Status: NEW
>           Severity: enhancement
>           Priority: P2
>          Component: math
>         AssignedTo: unassigned@sourceware.org
>         ReportedBy: marc.glisse@normalesup.org
>     Classification: Unclassified
> 
> 
> Hello,
> 
> this is very minor, and I don't even know what platforms use this file, but in
> ieee754/dbl-64/wordsize-64/s_finite.c:
> 
> int
> __finite(double x)
> {
>   int64_t lx;
>   EXTRACT_WORDS64(lx,x);
>   return
> (int)((uint64_t)((lx&INT64_C(0x7fffffffffffffff))-INT64_C(0x7ff0000000000000))>>63);
> }
>
It could be simplified more. Constants are  not necessary here. I will
post patch to libc-alpha. 
> The first constant 0x7fffffffffffffff is unnecessary, it would work just as
> well with 0x7ff0000000000000, so there is only one constant loaded. The same
> applies to the 32 bit version, but for platforms like x86 that embed 32 bit
> constants in the instruction it probably wouldn't matter.
> 
> -- 
> Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.



  parent reply	other threads:[~2013-04-21 10:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-21 10:06 marc.glisse at normalesup dot org
2013-04-21 10:54 ` [Bug math/15384] " neleai at seznam dot cz
2013-04-21 10:54 ` Ondřej Bílka [this message]
2013-04-21 11:03 ` ondra at iuuk dot mff.cuni.cz
2013-04-21 14:39 ` ondra at iuuk dot mff.cuni.cz
2013-04-21 14:46 ` ondra at iuuk dot mff.cuni.cz
2013-04-21 15:44 ` marc.glisse at normalesup dot org
2013-04-21 15:59 ` marc.glisse at normalesup dot org
2013-04-21 17:27 ` ondra at iuuk dot mff.cuni.cz
2013-04-21 18:06 ` marc.glisse at normalesup dot org
2013-04-22  8:32 ` ondra at iuuk dot mff.cuni.cz
2014-06-13 18:22 ` fweimer at redhat dot com
2015-09-17 16:48 ` cvs-commit at gcc dot gnu.org
2015-09-17 16:49 ` jsm28 at gcc dot gnu.org

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=20130421103937.GA9642@domone.kolej.mff.cuni.cz \
    --to=neleai@seznam.cz \
    --cc=glibc-bugs@sourceware.org \
    --cc=sourceware-bugzilla@sourceware.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).