public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amonakov at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/43494] [4.4/4.5/4.6 Regression] Overlooked dependency causes wrong scheduling, wrong code
Date: Wed, 21 Jul 2010 10:07:00 -0000 [thread overview]
Message-ID: <20100721100726.15237.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43494-578@http.gcc.gnu.org/bugzilla/>
------- Comment #21 from amonakov at gcc dot gnu dot org 2010-07-21 10:07 -------
(In reply to comment #20)
> (Even sel-sched apparently does not use cselib, that's surprising!)
Offtopic: yes, using cselib in sel-sched is not quite straightforward, since we
need it to work on arbitrary regions (as I understand cselib is designed to
work on EBBs).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43494
next prev parent reply other threads:[~2010-07-21 10:07 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 17:34 [Bug c/43494] New: gcc.c-torture/execute/vector-2.c fails with -fpic/-fPIC ghazi at gcc dot gnu dot org
2010-03-23 17:37 ` [Bug c/43494] " ghazi at gcc dot gnu dot org
2010-03-23 18:23 ` [Bug rtl-optimization/43494] " pinskia at gcc dot gnu dot org
2010-07-13 9:43 ` steven at gcc dot gnu dot org
2010-07-17 23:28 ` steven at gcc dot gnu dot org
2010-07-18 17:21 ` steven at gcc dot gnu dot org
2010-07-18 17:30 ` steven at gcc dot gnu dot org
2010-07-18 17:40 ` steven at gcc dot gnu dot org
2010-07-18 17:48 ` steven at gcc dot gnu dot org
2010-07-19 19:04 ` steven at gcc dot gnu dot org
2010-07-20 8:25 ` amonakov at gcc dot gnu dot org
2010-07-20 13:20 ` steven at gcc dot gnu dot org
2010-07-20 13:23 ` steven at gcc dot gnu dot org
2010-07-20 13:57 ` steven at gcc dot gnu dot org
2010-07-20 14:14 ` amonakov at gcc dot gnu dot org
2010-07-20 17:56 ` [Bug rtl-optimization/43494] Overlooked dependency causes wrong scheduling, wrong code steven at gcc dot gnu dot org
2010-07-20 18:08 ` [Bug rtl-optimization/43494] [4.4/4.5/4.6 Regression] " steven at gcc dot gnu dot org
2010-07-21 8:10 ` rguenth at gcc dot gnu dot org
2010-07-21 8:22 ` steven at gcc dot gnu dot org
2010-07-21 8:32 ` amonakov at gcc dot gnu dot org
2010-07-21 9:28 ` steven at gcc dot gnu dot org
2010-07-21 9:33 ` steven at gcc dot gnu dot org
2010-07-21 9:49 ` steven at gcc dot gnu dot org
2010-07-21 10:07 ` amonakov at gcc dot gnu dot org [this message]
2010-07-22 8:47 ` rguenth at gcc dot gnu dot org
2010-08-17 13:14 ` bernds at gcc dot gnu dot org
2010-08-18 10:50 ` steven at gcc dot gnu dot org
2010-08-18 14:36 ` bernds at gcc dot gnu dot org
2010-08-18 19:00 ` jakub at gcc dot gnu dot org
2010-08-19 13:39 ` bernds at gcc dot gnu dot org
2010-09-10 23:16 ` aoliva at gcc dot gnu dot org
[not found] <bug-43494-4@http.gcc.gnu.org/bugzilla/>
2010-10-01 12:03 ` jakub at gcc dot gnu.org
2011-01-13 10:51 ` aoliva at gcc dot gnu.org
2011-01-13 10:56 ` rguenther at suse dot de
2011-01-27 11:10 ` ebotcazou at gcc dot gnu.org
2011-02-03 6:05 ` aoliva at gcc dot gnu.org
2011-02-03 6:08 ` aoliva at gcc dot gnu.org
2011-02-09 22:52 ` sje at cup dot hp.com
2011-02-09 22:59 ` jakub at gcc dot gnu.org
2011-02-09 23:44 ` sje at cup dot hp.com
2011-02-10 7:03 ` ebotcazou at gcc dot gnu.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=20100721100726.15237.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).