public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/16951] [3.5 regression] ICE in make_decl_rtl with recursion in C++ constructor (-O1)
Date: Tue, 10 Aug 2004 00:16:00 -0000 [thread overview]
Message-ID: <20040810001623.13194.qmail@sourceware.org> (raw)
In-Reply-To: <20040809214639.16951.rjpeters@klab.caltech.edu>
------- Additional Comments From pinskia at gcc dot gnu dot org 2004-08-10 00:16 -------
: Search converges between 2004-07-29-trunk (#498) and 2004-07-30-trunk (#499).
Hmm, I did a -fdump-tree-vars to find out why this was ICE and I noticed that before, it was inlining
the constructor once and after it was inlining it a couple of times. Also after it removed some variables
which it should not be removed from scope.
--
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |critical
Component|c++ |tree-optimization
Summary|[3.5 regression] ICE in |[3.5 regression] ICE in
|make_decl_rtl with recursion|make_decl_rtl with recursion
|in C++ constructor |in C++ constructor (-O1)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16951
next prev parent reply other threads:[~2004-08-10 0:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 21:46 [Bug c++/16951] New: ICE with recursion in C++ constructor rjpeters at klab dot caltech dot edu
2004-08-09 21:47 ` [Bug c++/16951] " rjpeters at klab dot caltech dot edu
2004-08-09 21:48 ` rjpeters at klab dot caltech dot edu
2004-08-09 22:39 ` [Bug c++/16951] [3.5 regression] ICE in make_decl_rtl " bangerth at dealii dot org
2004-08-10 0:16 ` pinskia at gcc dot gnu dot org [this message]
2004-08-10 1:35 ` [Bug tree-optimization/16951] [3.5 regression] ICE in make_decl_rtl with recursion in C++ constructor (-O1) pinskia at gcc dot gnu dot org
2004-09-21 13:48 ` [Bug tree-optimization/16951] [4.0 " pinskia at gcc dot gnu dot org
2004-12-02 18:37 ` pinskia at gcc dot gnu dot org
2004-12-09 22:09 ` pinskia at gcc dot gnu dot org
2004-12-11 22:20 ` pinskia at gcc dot gnu dot org
2004-12-13 21:04 ` cvs-commit at gcc dot gnu dot org
2004-12-13 21:12 ` pinskia at gcc dot gnu dot org
2004-12-13 21:18 ` rjpeters at klab dot caltech dot edu
2004-12-23 19:37 ` cvs-commit at gcc dot gnu dot org
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=20040810001623.13194.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).