public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@dberlin.org>
To: pinskia at gcc dot gnu dot org <gcc-bugzilla@gcc.gnu.org>
Cc: gcc-bugs@gcc.gnu.org
Subject: Re: [Bug debug/19367] [4.0 Regression] ICE: tree_check in lookup_local_die with local `using'
Date: Mon, 10 Jan 2005 22:55:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.60.0501101754460.23298@dberlin.org> (raw)
In-Reply-To: <20050110215656.12260.qmail@sourceware.org>



On Mon, 10 Jan 2005, pinskia at gcc dot gnu dot org wrote:

>
> ------- Additional Comments From pinskia at gcc dot gnu dot org  2005-01-10 21:56 -------
> Confirmed, I think this is the boost ICE.
>

This happens because the orig_decl that we are trying to use in emitting 
the using decl info appears to have been trashed or garbage collected 
before we emit it.

I think i know why.


  reply	other threads:[~2005-01-10 22:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-10 21:39 [Bug c++/19367] New: 4.0: " gcc-bugzilla at gcc dot gnu dot org
2005-01-10 21:56 ` [Bug debug/19367] [4.0 Regression] " pinskia at gcc dot gnu dot org
2005-01-10 22:55   ` Daniel Berlin [this message]
2005-01-10 22:55 ` dberlin at dberlin dot org
2005-01-11  0:53 ` pinskia at gcc dot gnu dot org
2005-01-11  1:32 ` giovannibajo at libero dot it
2005-01-11  1:36 ` [Bug c++/19367] " pinskia at gcc dot gnu dot org
2005-01-11  1:42 ` pinskia at gcc dot gnu dot org
2005-01-19 18:41 ` pinskia at gcc dot gnu dot org
2005-01-25 16:11 ` pinskia at gcc dot gnu dot org
2005-01-31  2:11 ` mmitchel at gcc dot gnu dot org
2005-01-31  4:08 ` cvs-commit at gcc dot gnu dot org
2005-01-31  4:13 ` mmitchel at gcc dot gnu dot org
2005-02-28 15:16 ` 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=Pine.LNX.4.60.0501101754460.23298@dberlin.org \
    --to=dberlin@dberlin.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-bugzilla@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).