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/54358] ICE in output_pic_addr_const
Date: Thu, 23 Aug 2012 14:10:00 -0000	[thread overview]
Message-ID: <bug-54358-4-OjSD4Vzy3o@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54358-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-08-23 14:10:30 UTC ---
If inline-asm is not involved, sure.  But inline asm is a low level interface,
where it is user responsibility to supply correct constraints, we have some
quick measures, like a segfault handler if compiler segfaults during outputting
of an inline asm pattern, we emit an error instead of ICE, but that doesn't
handle assertion failures/aborts.  There are simply way too many things with
inline asm you can shoot yourself.  The gcc documentation says that p
constraint must be accompanied with address_operand check, which inline asm
can't provide, so the p constraint is probably never suitable for inline asm.


      parent reply	other threads:[~2012-08-23 14:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-23 11:45 [Bug c/54358] New: " alexander.adam at informatik dot tu-chemnitz.de
2012-08-23 11:46 ` [Bug c/54358] " alexander.adam at informatik dot tu-chemnitz.de
2012-08-23 11:48 ` rguenth at gcc dot gnu.org
2012-08-23 11:54 ` [Bug target/54358] " rguenth at gcc dot gnu.org
2012-08-23 13:30 ` jakub at gcc dot gnu.org
2012-08-23 13:49 ` alexander.adam at informatik dot tu-chemnitz.de
2012-08-23 14:10 ` jakub at gcc dot gnu.org [this message]

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-54358-4-OjSD4Vzy3o@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).