public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anemo at mba dot ocn dot ne dot jp" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/28126] gcc moves an expensive instruction outside of a conditional
Date: Thu, 13 Jul 2006 14:58:00 -0000	[thread overview]
Message-ID: <20060713145846.25538.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28126-12556@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from anemo at mba dot ocn dot ne dot jp  2006-07-13 14:58 -------
(In reply to comment #2)
> Although I don't know much about the instruction scheduling, I had
> a similar problem on SH and it was workarounded with emitting blockage
> insns.  The patch below might work for you, though I'm not sure if
> it's the right thing to do.

Thanks.  With this patch, gcc 4.1.1 produces expected output.
It seems gcc 4.2 does not move rdhwr before branch without this patch, but I
can not see why.


-- 


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


  parent reply	other threads:[~2006-07-13 14:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-21 16:04 [Bug c/28126] New: " anemo at mba dot ocn dot ne dot jp
2006-06-21 16:36 ` [Bug target/28126] " daney at gcc dot gnu dot org
2006-06-22  4:46 ` kkojima at gcc dot gnu dot org
2006-07-06 16:20 ` anemo at mba dot ocn dot ne dot jp
2006-07-12 16:08 ` drow at gcc dot gnu dot org
2006-07-13 14:42 ` anemo at mba dot ocn dot ne dot jp
2006-07-13 14:58 ` anemo at mba dot ocn dot ne dot jp [this message]
2006-07-21 16:34 ` anemo at mba dot ocn dot ne dot jp
2006-07-30 10:56 ` rsandifo at gcc dot gnu dot org
2006-08-03 21:07 ` rsandifo at gcc dot gnu dot org
2006-08-05 15:48 ` anemo at mba dot ocn dot ne dot jp
2008-09-07 17:33 ` daney at gcc dot gnu dot org
2008-09-08 19:49 ` rdsandiford at googlemail dot com

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=20060713145846.25538.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).