public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, kalbun@inwind.it,
	nobody@gcc.gnu.org
Subject: Re: c++/8226: g++ unable to complete compilation
Date: Fri, 25 Oct 2002 15:25:00 -0000	[thread overview]
Message-ID: <20021025222503.11621.qmail@sources.redhat.com> (raw)

Synopsis: g++ unable to complete compilation

State-Changed-From-To: open->closed
State-Changed-By: bangerth
State-Changed-When: Fri Oct 25 15:25:03 2002
State-Changed-Why:
    I cannot reproduce this, even with -O3. With gcc3.2.1pre
    and 3.3 CVS, the compile times are two to three times as
    long as with 2.95, but memory requirements are not much
    higher.
    
    Note also that gcc2.96 is not (and has never been) an
    officially supported version of gcc. You should contact
    Red Hat or Mandrake if this is important to you.
    
    For those wanting to reproduce my experiments, I attach
    a modified version of the file that can also be compiled
    with recent gccs (add std:: and typename in some places,
    etc, but nothing fundamental).

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8226


             reply	other threads:[~2002-10-25 22:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-25 15:25 bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-14 12:46 kalbun

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=20021025222503.11621.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=kalbun@inwind.it \
    --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).