public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: reichelt@igpm.rwth-aachen.de
To: christianbiere@gmx.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: optimization/8178: [3.4 regression] __builtin_ffs broken with -march=k6
Date: Mon, 28 Apr 2003 14:48:00 -0000	[thread overview]
Message-ID: <20030428144843.1197.qmail@sources.redhat.com> (raw)

Old Synopsis: __builtin_ffs broken
New Synopsis: [3.4 regression] __builtin_ffs broken with -march=k6

State-Changed-From-To: closed->analyzed
State-Changed-By: reichelt
State-Changed-When: Mon Apr 28 14:48:43 2003
State-Changed-Why:
    As Falk pointed out, __builtin_ffs broken is still broken
    on mainline with -march=k6. The tests ffs-1.c, ffs-2.c
    from the testsuite Eric mentioned also still fail on mainline.
    
    Since this all works on the 3.3 branch, we have a regression.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8178


                 reply	other threads:[~2003-04-28 14:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030428144843.1197.qmail@sources.redhat.com \
    --to=reichelt@igpm.rwth-aachen.de \
    --cc=christianbiere@gmx.de \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).