public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Robert Schiele <rschiele@uni-mannheim.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: inline-asm/10402: [3.3/3.4 regression] [i486] ICE in merge_assigned_reloads, at reload1.c:6134 Date: Fri, 18 Apr 2003 06:06:00 -0000 [thread overview] Message-ID: <20030418060600.14674.qmail@sources.redhat.com> (raw) The following reply was made to PR inline-asm/10402; it has been noted by GNATS. From: Robert Schiele <rschiele@uni-mannheim.de> To: rth@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, shensche@kodeaffe.de, gcc-gnats@gcc.gnu.org Cc: Subject: Re: inline-asm/10402: [3.3/3.4 regression] [i486] ICE in merge_assigned_reloads, at reload1.c:6134 Date: Fri, 18 Apr 2003 08:05:13 +0200 --PNTmBPCT7hxwcZjr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 18, 2003 at 03:45:12AM -0000, rth@gcc.gnu.org wrote: > The code is illegal. The same variable can't be the target > of two outputs. =20 You mean because of the variable 'f'? Doesn't make a difference whether the second output is a different one. Cha= nge this line and the one above to: int f, g; asm volatile("" :"=3DS" (f), "=3DD" (g) :); The same thing happens. So we have an ice-on-legal-and-illegal-code. ;-) Robert --=20 Robert Schiele Tel.: +49-621-181-2517 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de --PNTmBPCT7hxwcZjr Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE+n5WZxcDFxyGNGNcRAh56AKCuHP0Q41K4DnnqgIXqWlq55gM5KgCfdYtx 8U9tRw8gfH19eLKYKV2Mk2c= =cFE3 -----END PGP SIGNATURE----- --PNTmBPCT7hxwcZjr--
next reply other threads:[~2003-04-18 6:06 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-18 6:06 Robert Schiele [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-18 3:45 rth 2003-04-18 3:45 rth 2003-04-14 18:18 bangerth
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=20030418060600.14674.qmail@sources.redhat.com \ --to=rschiele@uni-mannheim.de \ --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).