public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: falk.hueffner@student.uni-tuebingen.de
To: Richard.Zidlicky@stud.informatik.uni-erlangen.de,
	gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	schwab@suse.de, zippel@linux-m68k.org
Subject: Re: inline-asm/5570: wrong code generated for asm statements, 3.0.3
Date: Fri, 02 May 2003 23:47:00 -0000	[thread overview]
Message-ID: <20030502234711.20640.qmail@sources.redhat.com> (raw)

Synopsis: wrong code generated for asm statements, 3.0.3

State-Changed-From-To: open->closed
State-Changed-By: falk
State-Changed-When: Fri May  2 23:47:10 2003
State-Changed-Why:
    My m68k is somewhat rusty, but the bug here seems to be that #106 is
    put into register D5, although D0 was explicitly requested (trap
    parameter).  I can reproduce this with gcc 3.0.4, but not with 3.2.3
    anymore.  So I close this bug.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5570


                 reply	other threads:[~2003-05-02 23:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030502234711.20640.qmail@sources.redhat.com \
    --to=falk.hueffner@student.uni-tuebingen.de \
    --cc=Richard.Zidlicky@stud.informatik.uni-erlangen.de \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=schwab@suse.de \
    --cc=zippel@linux-m68k.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).