public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: inline-asm/9910: gcc dies on inline assembly Date: Mon, 03 Mar 2003 23:16:00 -0000 [thread overview] Message-ID: <20030303231601.2608.qmail@sources.redhat.com> (raw) The following reply was made to PR inline-asm/9910; it has been noted by GNATS. From: Richard Henderson <rth@redhat.com> To: Zack Weinberg <zack@codesourcery.com> Cc: jay@remotepoint.com, gcc-gnats@gcc.gnu.org, gcc@sources.redhat.com, dies@sources.redhat.com Subject: Re: inline-asm/9910: gcc dies on inline assembly Date: Mon, 3 Mar 2003 15:12:54 -0800 On Sun, Mar 02, 2003 at 05:19:31PM -0800, Zack Weinberg wrote: > gcc should not ICE, but this is emphatically not correct code. I wonder if the thing to do is have instantiate_virtual_regs, when it sees that instantiation is not possible, and that the target insn is an asm, issue an error message and remove the insn from the instruction stream. I really can't think of any other solution. r~
next reply other threads:[~2003-03-03 23:16 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-03 23:16 Richard Henderson [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-11 21:28 hubicka 2003-03-03 23:46 Zack Weinberg 2003-03-03 1:26 Zack Weinberg 2003-03-03 0:56 jay
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=20030303231601.2608.qmail@sources.redhat.com \ --to=rth@redhat.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).