public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/38449] delay branch scheduling follows REG_CROSSING_JUMP jumps indiscriminately
Date: Mon, 08 Dec 2008 20:08:00 -0000	[thread overview]
Message-ID: <20081208200602.25250.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38449-5394@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from steven at gcc dot gnu dot org  2008-12-08 20:06 -------
What is target dependent about this, that you need a target hook for it?


-- 

steven at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2008-12-08 20:06:02
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38449


  reply	other threads:[~2008-12-08 20:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-08 19:34 [Bug rtl-optimization/38449] New: " amylaar at gcc dot gnu dot org
2008-12-08 20:08 ` steven at gcc dot gnu dot org [this message]
2008-12-08 20:37 ` [Bug rtl-optimization/38449] " amylaar at gcc dot gnu dot org
2009-03-04 22:38 ` amylaar at gcc dot gnu dot org
2009-03-05  0:30 ` amylaar at gcc dot gnu dot org
     [not found] <bug-38449-4@http.gcc.gnu.org/bugzilla/>
2012-09-30 19:26 ` amylaar at gcc dot gnu.org
2013-04-18 21:49 ` steven at gcc dot gnu.org
2013-04-22 14:10 ` amylaar 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=20081208200602.25250.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).