public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: nathan@gcc.gnu.org
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c++/2975
Date: Mon, 28 May 2001 02:56:00 -0000	[thread overview]
Message-ID: <20010528095602.20178.qmail@sourceware.cygnus.com> (raw)

The following reply was made to PR c++/2975; it has been noted by GNATS.

From: nathan@gcc.gnu.org
To: gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org, ral@hotmail.com
Cc:  
Subject: Re: c++/2975
Date: 28 May 2001 09:49:11 -0000

 Synopsis: Compiler segfaults compiling Qt 2.3.0
 
 State-Changed-From-To: open->analyzed
 State-Changed-By: nathan
 State-Changed-When: Mon May 28 02:49:11 2001
 State-Changed-Why:
     I attach an emailed source file. This does segfault at -O4.
     gcc 2.95 does not seg fault, but produces errors earlier
     on. I'm leaving this as high priority for the moment
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2975&database=gcc


             reply	other threads:[~2001-05-28  2:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-28  2:56 nathan [this message]
2001-06-05  6:46 c++/2975 Nathan Sidwell
2001-06-05 10:16 c++/2975 mmitchel
2001-06-05 13:46 c++/2975 mmitchel

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=20010528095602.20178.qmail@sourceware.cygnus.com \
    --to=nathan@gcc.gnu.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).