public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/27437] [4.2 Regression] -O3 regression due to SEE
Date: Fri, 05 May 2006 16:49:00 -0000 [thread overview]
Message-ID: <20060505164908.19307.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27437-682@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from pinskia at gcc dot gnu dot org 2006-05-05 16:49 -------
(In reply to comment #7)
>
> You are right. Using next_nonnote_insn/prev_nonnote_insn won't solve -O3
> (without -g). One real problem is SEE can't determine if SEE is safe by just
> looking at next_nonnote_insn/prev_nonnote_insn. The relevant insn may be a few
> more insns away. Denis, do you have a patch to address this?
Maybe the real question is why did you not raise this publicly when it was
being reviewed. Your terse style of reporting problems after the fact hurt
your crediablity (if there is any left now).
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-valid-code
Summary|[4.2 Regression]: -O3 |[4.2 Regression] -O3
|regression due to SEE |regression due to SEE
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27437
next prev parent reply other threads:[~2006-05-05 16:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 19:11 [Bug rtl-optimization/27437] New: [4.2 Regression]: " hjl at lucon dot org
2006-05-04 19:22 ` [Bug rtl-optimization/27437] " pinskia at gcc dot gnu dot org
2006-05-04 23:01 ` pinskia at gcc dot gnu dot org
2006-05-05 12:39 ` reichelt at gcc dot gnu dot org
2006-05-05 12:42 ` reichelt at gcc dot gnu dot org
2006-05-05 13:02 ` hjl at lucon dot org
2006-05-05 15:04 ` pinskia at gcc dot gnu dot org
2006-05-05 15:46 ` hjl at lucon dot org
2006-05-05 15:49 ` hjl at lucon dot org
2006-05-05 16:49 ` pinskia at gcc dot gnu dot org [this message]
2006-05-05 21:15 ` [Bug rtl-optimization/27437] [4.2 Regression] " pinskia at gcc dot gnu dot org
2006-05-05 22:18 ` pinskia at gcc dot gnu dot org
2006-05-05 22:22 ` pinskia at gcc dot gnu dot org
2006-05-07 8:24 ` [Bug rtl-optimization/27437] -O2 -fsee failures on x86 pinskia at gcc dot gnu dot org
2006-05-29 22:31 ` pinskia at gcc dot gnu dot org
2006-05-29 22:32 ` pinskia at gcc dot gnu dot org
2006-05-29 23:04 ` pinskia at gcc dot gnu dot org
2006-05-31 9:36 ` reichelt at gcc dot gnu dot org
2006-05-31 14:05 ` fxcoudert at gcc dot gnu dot org
2006-05-31 17:31 ` hjl at lucon 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=20060505164908.19307.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).