public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Richard Zidlicky <rz@linux-m68k.org>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: middle-end/7594: [m68k] ICE on legal code associated with simplify-rtx
Date: Sun, 11 May 2003 21:16:00 -0000	[thread overview]
Message-ID: <20030511211601.13878.qmail@sources.redhat.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 990 bytes --]

The following reply was made to PR middle-end/7594; it has been noted by GNATS.

From: Richard Zidlicky <rz@linux-m68k.org>
To: Dara Hazeghi <dhazeghi@yahoo.com>
Cc: gcc-gnats@gcc.gnu.org, law@redhat.com
Subject: Re: middle-end/7594: [m68k] ICE on legal code associated with simplify-rtx
Date: Sun, 11 May 2003 22:37:46 +0200

 On Fri, May 09, 2003 at 04:34:25PM -0700, Dara Hazeghi wrote:
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- 
 > trail&database=gcc&pr=7594
 
 Hi,
 
 > I can confirm that this bug is still present on 3.2 and 3.3 branch but  
 > does not occur on mainline (20030508) gcc cross compiler. Jeff Law,  
 > you're listed as m68k maintainer. Would there be any interest in fixing  
 > this in the 3.3 branch after 3.3.0? Thanks,
 
 thanks for looking at it. The bug is pretty severe, not only did it
 break glibc but even medium sized packages won´t compile without a fix.
 I would certainly be very interested to know if my patch is correct.
 
 Richard


             reply	other threads:[~2003-05-11 21:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-11 21:16 Richard Zidlicky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-09 23:36 Dara Hazeghi

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=20030511211601.13878.qmail@sources.redhat.com \
    --to=rz@linux-m68k.org \
    --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).