public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Michael H. Cox" <mhcox08809@yahoo.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: RE: c/3461: Internal compiler error while compiling ncurses-5.2 comp_hash.c (do_alloc.c)
Date: Wed, 24 Apr 2002 15:36:00 -0000 [thread overview]
Message-ID: <20020424223602.17528.qmail@sources.redhat.com> (raw)
The following reply was made to PR c/3461; it has been noted by GNATS.
From: "Michael H. Cox" <mhcox08809@yahoo.com>
To: <rodrigc@gcc.gnu.org>,
<gcc-bugs@gcc.gnu.org>,
<gcc-prs@gcc.gnu.org>,
<nobody@gcc.gnu.org>,
<gcc-gnats@gcc.gnu.org>
Cc:
Subject: RE: c/3461: Internal compiler error while compiling ncurses-5.2 comp_hash.c (do_alloc.c)
Date: Wed, 24 Apr 2002 16:30:35 -0600
In ncurses-5.2-7, the internal compiler error for comp_hash.c doesn't occur
under Cygwin.
Mike
> -----Original Message-----
> From: rodrigc@gcc.gnu.org [mailto:rodrigc@gcc.gnu.org]
> Sent: Saturday, February 23, 2002 8:04 PM
> To: gcc-bugs@gcc.gnu.org; gcc-prs@gcc.gnu.org;
> mhcox@BlueZooSoftware.com; nobody@gcc.gnu.org
> Subject: Re: c/3461: Internal compiler error while compiling ncurses-5.2
> comp_hash.c (do_alloc.c)
>
>
> Synopsis: Internal compiler error while compiling ncurses-5.2
> comp_hash.c (do_alloc.c)
>
> State-Changed-From-To: open->feedback
> State-Changed-By: rodrigc
> State-Changed-When: Sat Feb 23 19:03:49 2002
> State-Changed-Why:
> I can't reproduce this problem with gcc 3.0.4 under Linux.
> Is it still a problem with gcc 3.0.4 under Cygwin?
>
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&data
base=gcc&pr=3461
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
next reply other threads:[~2002-04-24 22:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-24 15:36 Michael H. Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-24 15:52 rodrigc
2002-02-23 19:05 rodrigc
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=20020424223602.17528.qmail@sources.redhat.com \
--to=mhcox08809@yahoo.com \
--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).