public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub 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: Mon, 13 Dec 2010 10:59:00 -0000 [thread overview]
Message-ID: <bug-46915-4-YJe11l1jVD@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
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> 2010-12-13 10:59:28 UTC ---
Yeah, the insn count for asm is just a guess. You should never put inline asm
into a delay slot, you really don't know how big it is or if it is suitable for
the delay slot.
I guess the bug is in checking just for ASM_INPUT, that should be also testing
extract_asm_operands () != NULL_RTX.
next prev parent reply other threads:[~2010-12-13 10:59 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 [this message]
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
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-YJe11l1jVD@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).