public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/19579] [3.3/3.4/4.0 regression] -march=i686 generates a bogus program for x86*
Date: Tue, 25 Jan 2005 23:09:00 -0000 [thread overview]
Message-ID: <20050125230915.12771.qmail@sourceware.org> (raw)
In-Reply-To: <20050123002852.19579.abulmo@club-internet.fr>
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-01-25 23:09 -------
Subject: Bug 19579
CVSROOT: /cvs/gcc
Module name: gcc
Changes by: jakub@gcc.gnu.org 2005-01-25 23:09:10
Modified files:
gcc : ChangeLog ifcvt.c
gcc/testsuite : ChangeLog
Added files:
gcc/testsuite/gcc.c-torture/execute: 20050124-1.c
Log message:
PR rtl-optimization/19579
* ifcvt.c (noce_try_cmove_arith): If emitting instructions to set up
both A and B, see if they don't clobber registers the other expr uses.
* gcc.c-torture/execute/20050124-1.c: New test.
Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&r1=2.7273&r2=2.7274
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ifcvt.c.diff?cvsroot=gcc&r1=1.178&r2=1.179
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/ChangeLog.diff?cvsroot=gcc&r1=1.4936&r2=1.4937
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gcc.c-torture/execute/20050124-1.c.diff?cvsroot=gcc&r1=NONE&r2=1.1
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19579
next prev parent reply other threads:[~2005-01-25 23:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-23 0:29 [Bug c/19579] New: -march=i686 generates a bogus program abulmo at club-internet dot fr
2005-01-23 0:31 ` [Bug target/19579] " pinskia at gcc dot gnu dot org
2005-01-23 21:15 ` [Bug target/19579] [3.3/3.4 regression] " reichelt at gcc dot gnu dot org
2005-01-23 21:32 ` [Bug target/19579] [3.3/3.4/4.0 " belyshev at depni dot sinp dot msu dot ru
2005-01-23 22:06 ` steven at gcc dot gnu dot org
2005-01-23 22:08 ` steven at gcc dot gnu dot org
2005-01-23 22:13 ` steven at gcc dot gnu dot org
2005-01-23 22:14 ` pinskia at gcc dot gnu dot org
2005-01-23 22:25 ` kazu at cs dot umass dot edu
2005-01-23 23:50 ` [Bug rtl-optimization/19579] [3.3/3.4/4.0 regression] -march=i686 generates a bogus program for x86* steven at gcc dot gnu dot org
2005-01-24 0:02 ` steven at gcc dot gnu dot org
2005-01-24 0:35 ` steven at gcc dot gnu dot org
2005-01-24 9:40 ` steven at gcc dot gnu dot org
2005-01-24 10:30 ` jakub at gcc dot gnu dot org
2005-01-24 11:31 ` jakub at gcc dot gnu dot org
2005-01-24 14:13 ` pinskia at gcc dot gnu dot org
2005-01-25 23:09 ` cvs-commit at gcc dot gnu dot org [this message]
2005-01-26 1:19 ` [Bug rtl-optimization/19579] [3.3/3.4 " pinskia at gcc dot gnu dot org
2005-02-10 20:35 ` cvs-commit at gcc dot gnu dot org
2005-02-10 20:42 ` [Bug rtl-optimization/19579] [3.3 " pinskia at gcc dot gnu dot org
2005-04-28 8:34 ` gdr at gcc dot gnu dot org
2005-05-01 7:23 ` cvs-commit at gcc dot gnu dot org
2005-05-01 13:17 ` pinskia at gcc dot gnu dot 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=20050125230915.12771.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).