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/53854] ICE in find_constant_pool_ref
Date: Tue, 10 Jul 2012 08:23:00 -0000 [thread overview]
Message-ID: <bug-53854-4-IEDtwhXPXc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53854-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53854
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEW
AssignedTo|jakub at gcc dot gnu.org |unassigned at gcc dot
| |gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-07-10 08:23:33 UTC ---
It is true that asm can occupy even zero bytes (or some bytes just in other
sections, but not in text section), so even allowing a single constant pool
reference in an inline asm might be too much (if you have thousands of such
inline asms next to each other). No idea where would you reject the constant
pool references for the asm, inline asm can use any kind of constraints.
next prev parent reply other threads:[~2012-07-10 8:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 13:05 [Bug target/53854] New: " jakub at gcc dot gnu.org
2012-07-04 13:15 ` [Bug target/53854] " jakub at gcc dot gnu.org
2012-07-04 13:25 ` jakub at gcc dot gnu.org
2012-07-04 17:17 ` uweigand at gcc dot gnu.org
2012-07-10 8:23 ` jakub at gcc dot gnu.org [this message]
2012-09-20 10:23 ` jakub at gcc dot gnu.org
2013-04-11 7:59 ` rguenth at gcc dot gnu.org
2013-05-23 8:25 ` dan at danny dot cz
2014-06-12 13:53 ` rguenth at gcc dot gnu.org
2014-08-26 18:04 ` dan at danny dot cz
2014-09-01 16:30 ` uweigand 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-53854-4-IEDtwhXPXc@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).