public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: kukuk@suse.de
Cc: gcc@gcc.gnu.org
Subject: Re: Illegal instruction on sparc32-linux
Date: Wed, 24 Apr 2002 07:07:00 -0000	[thread overview]
Message-ID: <20020424.064844.120470257.davem@redhat.com> (raw)
In-Reply-To: <20020419180943.A15551@suse.de>


Thorston, I believe we have discovered the cause of the
problems.  After I run some testsuites to check for regressions
I will update the GNATs entry for this bug and post the patch.

I will add you to the CC: of the GNATs PR so that you will know
when 3.1 CVS has the fix installed.

It turns out to be a generic sparc backend bug.

      reply	other threads:[~2002-04-24 13:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-18 13:18 Thorsten Kukuk
2002-04-18 13:32 ` Christian Jönsson
2002-04-18 14:51 ` David S. Miller
2002-04-19  2:51   ` Thorsten Kukuk
2002-04-19  3:40     ` David S. Miller
2002-04-19  4:45       ` Thorsten Kukuk
2002-04-19  9:03         ` David S. Miller
2002-04-19  9:20           ` Thorsten Kukuk
2002-04-24  7:07             ` David S. Miller [this message]

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=20020424.064844.120470257.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=kukuk@suse.de \
    /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).