public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Volker Reichelt <reichelt@igpm.rwth-aachen.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/8178: __builtin_ffs broken Date: Wed, 12 Mar 2003 12:36:00 -0000 [thread overview] Message-ID: <20030312123600.15162.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/8178; it has been noted by GNATS. From: Volker Reichelt <reichelt@igpm.rwth-aachen.de> To: christianbiere@gmx.de, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, rth@redhat.com, falk.hueffner@student.uni-tuebingen.de Cc: ebotcazou@libertysurf.fr Subject: Re: optimization/8178: __builtin_ffs broken Date: Wed, 12 Mar 2003 13:30:29 +0100 (CET) I can confirm that the problem is still present on k6. According to Phil's tester the problem for the ix86 was fixed between 2003-01-31 and 2003-02-01. Therefore I strongly suspect that the following patch (by Richard Henderson and Falk Hueffner) was responsible for the fix: http://gcc.gnu.org/ml/gcc-cvs/2003-02/msg00033.html That's why I'm asking you, Richard and Falk, could you please have a look at the patch, whether it really did fix things and if yes, why it doesn't fix the k6-issue and whether the fix can be backported to 3.3 or even 3.2? Thanks, Volker
next reply other threads:[~2003-03-12 12:36 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-12 12:36 Volker Reichelt [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-18 16:26 Falk Hueffner 2003-04-18 15:36 reichelt 2003-03-13 0:46 Richard Henderson 2003-03-10 15:46 Eric Botcazou 2003-03-10 15:06 Volker Reichelt
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=20030312123600.15162.qmail@sources.redhat.com \ --to=reichelt@igpm.rwth-aachen.de \ --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: linkBe 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).