public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Joseph Myers <jsm28@cam.ac.uk>
To: gcc-gnats@gcc.gnu.org
Cc: jsm28@cam.ac.uk
Subject: c/3120: __builtin_fsqrt still on mainline
Date: Mon, 11 Jun 2001 02:26:00 -0000 [thread overview]
Message-ID: <E159NwZ-0004kg-00@jsm28.trin.cam.ac.uk> (raw)
>Number: 3120
>Category: c
>Synopsis: __builtin_fsqrt still on mainline
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Jun 11 02:26:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: Joseph S. Myers
>Release: 3.1 20010609 (experimental)
>Organization:
none
>Environment:
System: Linux digraph 2.2.19 #1 Wed Mar 28 16:01:38 UTC 2001 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-cvs/configure --prefix=/opt/gcc/mainline --disable-shared --enable-threads=posix --with-system-zlib
>Description:
The mainline still has __builtin_fsqrt, where the 3.0 branch changed
to __builtin_sqrt. This sort of regression from branch to mainline
should be avoided - but has been present since the 28th of May.
http://gcc.gnu.org/ml/gcc-patches/2001-06/msg00394.html
>How-To-Repeat:
Work on the GCC manual and observe a bogus difference
branch-to-mainline, because this patch (including the doc changes) has
not been applied to the mainline.
>Fix:
Adapt http://gcc.gnu.org/ml/gcc-patches/2001-05/msg01939.html for the
mainline and apply it.
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2001-06-11 2:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-11 2:26 Joseph Myers [this message]
2001-06-22 3:33 jsm28
2001-12-14 13:07 aj
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=E159NwZ-0004kg-00@jsm28.trin.cam.ac.uk \
--to=jsm28@cam.ac.uk \
--cc=gcc-gnats@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).