public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jan Hubicka <jh@suse.cz>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: inline-asm/4823: [3.2/3.3/3.4 regression] gcc reports internal compiler error on legal code
Date: Mon, 24 Mar 2003 23:16:00 -0000	[thread overview]
Message-ID: <20030324224601.24795.qmail@sources.redhat.com> (raw)

The following reply was made to PR inline-asm/4823; it has been noted by GNATS.

From: Jan Hubicka <jh@suse.cz>
To: Steven Bosscher <s.bosscher@student.tudelft.nl>
Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org,
	rudd@cyberoptics.com, gcc-prs@gcc.gnu.org, rodrigc@gcc.gnu.org,
	jh@suse.cz
Subject: Re: inline-asm/4823: [3.2/3.3/3.4 regression] gcc reports internal compiler error on legal code
Date: Mon, 24 Mar 2003 23:38:02 +0100

 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4823
 > 
 > For Wolfgang's smaller testcase:
 > 
 > ---------------------------------
 > void
 > f (void)
 > {
 >  double result;
 >  asm volatile (
 >  " faddp %0, %1 \n\t"
 >  : "=&t" (result)
 >  : "u" (result),
 >    "0" (result)
 >  : "%st", "%st(1)", "%st(2)", "%st(3)",
 >    "%st(4)", "%st(5)", "%st(6)", "%st(7)"
 >  );
 > }
 > ------------------------
 > 
 > we now don't crash.  Instead we bail out with an error.
 > 
 > # gcc-3.3 -c 4823.c
 > 4823.c: In function `f':
 > 4823.c:5: error: output constraint 0 cannot be specified together with 
 > "st" clobber
 > 4823.c:8: confused by earlier errors, bailing out
 > # gcc-3.3 -c 4823.c -O
 > 4823.c: In function `f':
 > 4823.c:5: error: output constraint 0 cannot be specified together with 
 > "st" clobber
 > 4823.c:8: confused by earlier errors, bailing out
 > # gcc-3.3 -c 4823.c -O2
 > 4823.c: In function `f':
 > 4823.c:5: error: output constraint 0 cannot be specified together with 
 > "st" clobber
 > 4823.c:8: confused by earlier errors, bailing out
 > 
 > Honza, is this the correct behavior?
 Hmm, not really "confused by earlier errors, bailing out" means that
 compiler segfaulted.  It is different failure - the reg-stack is not
 really good at dealing with missformed asm constrains.  I believe I've
 sent a patch some time ago for similar problem, will try to dig it out,
 but probably next week - this week is bit too hectic for me.
 
 Honza
 > 
 > Greetz
 > Steven
 > 


             reply	other threads:[~2003-03-24 22:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-24 23:16 Jan Hubicka [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-24 19:46 Steven Bosscher

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=20030324224601.24795.qmail@sources.redhat.com \
    --to=jh@suse.cz \
    --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: 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).