public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Gabriel Dos_Reis <gdosreis@sophia.inria.fr>
To: ebotcazou@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/9279: [3.2 regression] [Sparc] combine bug
Date: Wed, 29 Jan 2003 01:26:00 -0000 [thread overview]
Message-ID: <20030129012601.7141.qmail@sources.redhat.com> (raw)
The following reply was made to PR optimization/9279; it has been noted by GNATS.
From: Gabriel Dos_Reis <gdosreis@sophia.inria.fr>
To: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de>
Cc: Matthias Klose <doko@cs.tu-berlin.de>,
Eric Botcazou <ebotcazou@libertysurf.fr>, ebotcazou@gcc.gnu.org,
frank@g-n-u.de, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: optimization/9279: [3.2 regression] [Sparc] combine bug
Date: Wed, 29 Jan 2003 02:25:50 +0100 (MET)
| > (2) possibly a wrong code generation -- David gave some
| > references.
|
| I must have missed this discussion, Could you give me a pointer?
Sorry, that is part of e-mail exhancge I had with Eric Dadid
yesterday. Quoting him:
This patch and the necessary PowerPC patch exposed other bugs in
the compiler regarding REG_EQUAL notes in loop unrolling:
2002-10-04 David Edelsohn <edelsohn@gnu.org>
* unroll.c (copy_loop_body): Remove REG_EQUAL note attached to
copied instruction if the note is not loop invariant.
The patches may have other co-dependencies we do not know about.
Eric agreed with him.
I would like to avoid last time minute patch chasing.
-- Gaby
next reply other threads:[~2003-01-29 1:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 1:26 Gabriel Dos_Reis [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-16 15:00 ebotcazou
2003-01-29 1:36 Gabriel Dos_Reis
2003-01-29 0:06 Christian Ehrhardt
2003-01-28 23:36 Eric Botcazou
2003-01-28 22:36 Matthias Klose
2003-01-28 22:16 Gabriel Dos_Reis
2003-01-28 20:56 Matthias Klose
2003-01-27 17:56 Eric Botcazou
2003-01-27 17:05 ebotcazou
2003-01-25 16:12 ebotcazou
2003-01-24 16:27 ebotcazou
2003-01-24 11:06 Christian Ehrhardt
2003-01-23 19:44 ebotcazou
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=20030129012601.7141.qmail@sources.redhat.com \
--to=gdosreis@sophia.inria.fr \
--cc=ebotcazou@gcc.gnu.org \
--cc=gcc-prs@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).