public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/46915] Wrong code is generated for conditional branch followed by zero length asm
Date: Wed, 22 Dec 2010 18:47:00 -0000	[thread overview]
Message-ID: <bug-46915-4-epDO8IrfSG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46915-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #15 from John David Anglin <danglin at gcc dot gnu.org> 2010-12-22 18:47:04 UTC ---
Author: danglin
Date: Wed Dec 22 18:46:57 2010
New Revision: 168177

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=168177
Log:
    Backport from mainline:
    2010-12-18  John David Anglin  <dave.anglin@nrc-cnrc.gc.ca>

    PR target/46915
    * config/pa/pa.c (branch_to_delay_slot_p): Use next_active_insn instead
    of next_real_insn.  Search forward checking for both ASM_INPUT and
    ASM_OPERANDS asms until exit condition is found.
    (branch_needs_nop_p): Likewise.
    (use_skip_p): New function.
    (output_cbranch): Use use_skip_p.
    (output_bb, output_bvb): Likewise.

    2009-06-25  John David Anglin  <dave.anglin@nrc-cnrc.gc.ca>

    PR target/40468
    * pa.c (branch_to_delay_slot_p, branch_needs_nop_p): New functions.
    (output_cbranch): Use new functions.
    (output_bb, output_bvb, output_dbra, output_movb): Likewise.


Modified:
    branches/gcc-4_4-branch/gcc/ChangeLog
    branches/gcc-4_4-branch/gcc/config/pa/pa.c


  parent reply	other threads:[~2010-12-22 18:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-12 22:48 [Bug target/46915] New: " danglin at gcc dot gnu.org
2010-12-13  2:45 ` [Bug target/46915] " dave at hiauly1 dot hia.nrc.ca
2010-12-13  2:45 ` dave at hiauly1 dot hia.nrc.ca
2010-12-13  2:50 ` dave at hiauly1 dot hia.nrc.ca
2010-12-13  3:59 ` dave at hiauly1 dot hia.nrc.ca
2010-12-13  3:59 ` dave at hiauly1 dot hia.nrc.ca
2010-12-13  9:35 ` amylaar at gcc dot gnu.org
2010-12-13 10:59 ` jakub at gcc dot gnu.org
2010-12-13 12:44 ` dave at hiauly1 dot hia.nrc.ca
2010-12-13 12:52 ` dave at hiauly1 dot hia.nrc.ca
2010-12-18 17:10 ` danglin at gcc dot gnu.org
2010-12-18 22:28 ` eike@sf-mail.de
2010-12-18 22:42 ` dave at hiauly1 dot hia.nrc.ca
2010-12-19 19:50 ` danglin at gcc dot gnu.org
2010-12-22 18:47 ` danglin at gcc dot gnu.org [this message]
2010-12-22 18:50 ` danglin at gcc dot gnu.org
2010-12-22 18:58 ` danglin 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=bug-46915-4-epDO8IrfSG@http.gcc.gnu.org/bugzilla/ \
    --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).