public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Zack Weinberg" <zackw@Stanford.EDU>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c++/1687: Extreme compile time regression from 2.95.2
Date: Sun, 01 Apr 2001 00:00:00 -0000	[thread overview]
Message-ID: <20010207184601.30121.qmail@sourceware.cygnus.com> (raw)

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

From: "Zack Weinberg" <zackw@Stanford.EDU>
To: Kelley Cook <kelley.cook@home.com>
Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: c++/1687: Extreme compile time regression from 2.95.2
Date: Wed, 7 Feb 2001 10:36:51 -0800

 On Tue, Feb 06, 2001 at 12:43:21PM -0800, Zack Weinberg wrote:
 > 
 > 	* optimize.c: Include hashtab.h.
 > 	(struct inline_data): Add tree_pruner field.
 > 	(expand_call_inline, expand_calls_inline): Call walk_tree with
 > 	id->tree_pruner for fourth argument, putting it into
 > 	no-duplicates mode.
 > 	(optimize_function): Create and destroy a hash table for
 > 	duplicate pruning, store it in id.tree_pruner.
 
 This survived an x86-linux bootstrap and reports the following test
 suite failures.  I do not know if they are regressions or not.
 
 FAIL: g++.dg/vtgc1.C scan-assembler (about 30 of these)
 FAIL: g++.ext/instantiate1.C not instantiated (test for errors, line 18)
 FAIL: g++.ext/instantiate1.C not instantiated (test for errors, line 20)
 FAIL: g++.jason/2371.C (test for excess errors)
 FAIL: g++.other/crash32.C (test for excess errors)
 FAIL: g++.other/loop2.C caused compiler crash
 
 zw
>From lerdsuwa@gcc.gnu.org Sun Apr 01 00:00:00 2001
From: lerdsuwa@gcc.gnu.org
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c++/117
Date: Sun, 01 Apr 2001 00:00:00 -0000
Message-id: <20010204113600.13429.qmail@sourceware.cygnus.com>
X-SW-Source: 2001-q1/msg00914.html
Content-length: 627

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

From: lerdsuwa@gcc.gnu.org
To: gcc-gnats@gcc.gnu.org, jsjacob@eclipsenetworks.com,
  martin@loewis.home.cs.tu-berlin.de, nobody@gcc.gnu.org
Cc:  
Subject: Re: c++/117
Date: 4 Feb 2001 11:28:25 -0000

 Synopsis: Internal compiler error 19970302 on SCO_SV 3.2 2 i386
 
 State-Changed-From-To: analyzed->closed
 State-Changed-By: lerdsuwa
 State-Changed-When: Sun Feb  4 03:28:25 2001
 State-Changed-Why:
     The bug appears to be fixed in the CVS.  Tested with Jan 23, 2001 snapshot.
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=117&database=gcc
>From aoliva@gcc.gnu.org Sun Apr 01 00:00:00 2001
From: aoliva@gcc.gnu.org
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c++/1882
Date: Sun, 01 Apr 2001 00:00:00 -0000
Message-id: <20010311190601.3356.qmail@sourceware.cygnus.com>
X-SW-Source: 2001-q1/msg02223.html
Content-length: 727

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

From: aoliva@gcc.gnu.org
To: bumgard@roguewave.com, gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org
Cc:  
Subject: Re: c++/1882
Date: 11 Mar 2001 19:01:18 -0000

 Synopsis: Compilation fails when a default constructor appears as the first argument in constructor template.
 
 State-Changed-From-To: open->closed
 State-Changed-By: aoliva
 State-Changed-When: Sun Mar 11 11:01:18 2001
 State-Changed-Why:
     This is the well-known parser error in G++, that can only be fixed with a parser rewrite.  I don't think it's worth keeping this bug report open; we all know about the problem.
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=1882&database=gcc


             reply	other threads:[~2001-04-01  0:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-01  0:00 Zack Weinberg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-11 21:46 Steven Bosscher
2003-04-11 19:36 Wolfgang Bangerth
2003-04-11 19:06 Steven Bosscher
2002-11-20 18:58 Wolfgang Bangerth
2002-11-10 14:16 Zack Weinberg
2002-11-10 13:56 Wolfgang Bangerth
2001-04-01  0:00 Zack Weinberg
2001-04-01  0:00 Zack Weinberg
2001-04-01  0:00 Zack Weinberg

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=20010207184601.30121.qmail@sourceware.cygnus.com \
    --to=zackw@stanford.edu \
    --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).