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 c++/24582] [4.0/4.1 regression] ICE in decl_jump_unsafe
Date: Sun, 30 Oct 2005 17:42:00 -0000	[thread overview]
Message-ID: <20051030174215.12628.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24582-280@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from pinskia at gcc dot gnu dot org  2005-10-30 17:42 -------
(In reply to comment #3)
> This is not mine after all.
As this was introduced before my patch which I had thought might had caused it.

This was caused by:
2005-10-13  Mark Mitchell  <mark@codesourcery.com>

        PR c++/20721
        * cp-tree.h (DECL_NONTRIVIALLY_INITIALIZED_P): New macro.
        * decl.c (duplicate_decls): Merge it into new declarations.
        (decl_jump_unsafe): Use it, rather than DECL_INITIAL.
        (cp_finish_decl): Set it, when appropriate.


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mmitchel at gcc dot gnu dot
                   |                            |org
            Summary|[4.1 regression] ICE in     |[4.0/4.1 regression] ICE in
                   |decl_jump_unsafe            |decl_jump_unsafe
   Target Milestone|4.1.0                       |4.0.3


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24582


  parent reply	other threads:[~2005-10-30 17:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-29 22:09 [Bug c++/24582] New: [4.1 " steven at gcc dot gnu dot org
2005-10-29 22:10 ` [Bug c++/24582] " steven at gcc dot gnu dot org
2005-10-29 22:23 ` pinskia at gcc dot gnu dot org
2005-10-30 17:30 ` pinskia at gcc dot gnu dot org
2005-10-30 17:37 ` pinskia at gcc dot gnu dot org
2005-10-30 17:42 ` pinskia at gcc dot gnu dot org [this message]
2005-10-31  6:44 ` [Bug c++/24582] [4.0/4.1 " mmitchel at gcc dot gnu dot org
2005-10-31 19:22 ` pinskia at gcc dot gnu dot org
2005-11-01  4:45 ` pinskia at gcc dot gnu dot org
2005-11-03  7:09 ` mmitchel at gcc dot gnu dot org
2005-11-03 15:06 ` pinskia at gcc dot gnu dot org
2005-11-03 15:13 ` pinskia at gcc dot gnu dot org
2005-11-03 15:13 ` pinskia at gcc dot gnu dot org
2006-01-21 23:42 ` pinskia 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=20051030174215.12628.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).