public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: giovannibajo@libero.it
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	mark_lee_hamilton@worldnet.att.net, nobody@gcc.gnu.org
Subject: Re: target/9697: [m68k]invalid instruction when building m68k cross in libiberty
Date: Sat, 10 May 2003 07:49:00 -0000	[thread overview]
Message-ID: <20030510074916.10870.qmail@sources.redhat.com> (raw)

Synopsis: [m68k]invalid instruction when building m68k cross in libiberty

State-Changed-From-To: open->feedback
State-Changed-By: bajo
State-Changed-When: Sat May 10 07:49:16 2003
State-Changed-Why:
    See Dara's question.

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


             reply	other threads:[~2003-05-10  7:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-10  7:49 giovannibajo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-10  0:16 Dara Hazeghi
2003-02-26  0:46 Mark_Hamilton

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=20030510074916.10870.qmail@sources.redhat.com \
    --to=giovannibajo@libero.it \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=mark_lee_hamilton@worldnet.att.net \
    --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).