public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Steven Bosscher <s.bosscher@student.tudelft.nl>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/10023: g++ Internal Compiler Error at -O2-4
Date: Tue, 11 Mar 2003 11:16:00 -0000	[thread overview]
Message-ID: <20030311111602.22087.qmail@sources.redhat.com> (raw)

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

From: Steven Bosscher <s.bosscher@student.tudelft.nl>
To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org,
	jens.troeger@light-speed.de
Cc:  
Subject: Re: c++/10023: g++ Internal Compiler Error at -O2-4
Date: Tue, 11 Mar 2003 12:12:26 +0100

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10023
 
 Jens Troeger wrote:
  > i can send you the source files?
 
 Yes please.  Without the source we can of course not reproduce the 
 problem, or see if the issue has been fixed in later versions. 
  Preprocessed source is welcome, a small test case is even more welcome.
 
 Please read the instructions on "http://gcc.gnu.org/bugs.html#report" to 
 see how you can help out best.
 
 Note that the "prerelease" (there is no "official" GCC 2.95.4 release) 
 you are using is almost two years old.  The problem may have been fixed 
 in GCC 3.x.
 
 Greetz
 Steven
 
 


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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-11 11:16 Steven Bosscher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-11 22:56 Jens Troeger
2003-03-11 15:01 bangerth
2003-03-11  7:36 jens.troeger

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=20030311111602.22087.qmail@sources.redhat.com \
    --to=s.bosscher@student.tudelft.nl \
    --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).