public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Daniel Berlin" <dberlin@dberlin.org>
To: gcc-bugzilla@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org
Subject: Re: [Bug tree-optimization/29585] [4.2/4.3 Regression] tree check: expected ssa_name, have var_decl in is_old_name, at tree-into-ssa.c:558
Date: Wed, 25 Oct 2006 12:12:00 -0000 [thread overview]
Message-ID: <4aca3dc20610250512x511a971bi9042db32e38ec43f@mail.gmail.com> (raw)
In-Reply-To: <20061025052300.19371.qmail@sourceware.org>
On 25 Oct 2006 05:23:00 -0000, pinskia at gcc dot gnu dot org
<gcc-bugzilla@gcc.gnu.org> wrote:
>
>
> ------- Comment #4 from pinskia at gcc dot gnu dot org 2006-10-25 05:22 -------
> _ZTCN33_GLOBAL__N_t.cc_00000000_2292CFAC11NullostreamE0_13basic_ostream
>
> # _ZTI13basic_ostream = V_MAY_DEF <_ZTI13basic_ostream_16>;
> # _ZTIN33_GLOBAL__N_t.cc_00000000_2292CFAC11NullostreamE = V_MAY_DEF
> <_ZTIN33_GLOBAL__N_t.cc_00000000_2292CFAC11NullostreamE_17>;
> # _ZTCN33_GLOBAL__N_t.cc_00000000_2292CFAC11NullostreamE0_13basic_ostream =
> V_MAY_DEF
> <_ZTCN33_GLOBAL__N_t.cc_00000000_2292CFAC11NullostreamE0_13basic_ostream>;
> # _ZTSN33_GLOBAL__N_t.cc_00000000_2292CFAC11NullostreamE = V_MAY_DEF
> <_ZTSN33_GLOBAL__N_t.cc_00000000_2292CFAC11NullostreamE>;
> # _ZTVN10__cxxabiv120__si_class_type_infoE = V_MAY_DEF
> <_ZTVN10__cxxabiv120__si_class_type_infoE>;
> # _ZTI8ios_base = V_MAY_DEF <_ZTI8ios_base>;
> # _ZTS13basic_ostream = V_MAY_DEF <_ZTS13basic_ostream>;
> # _ZTVN10__cxxabiv121__vmi_class_type_infoE = V_MAY_DEF
> <_ZTVN10__cxxabiv121__vmi_class_type_infoE>;
> # _ZTS8ios_base = V_MAY_DEF <_ZTS8ios_base>;
> # _ZTVN10__cxxabiv117__class_type_infoE = V_MAY_DEF
> <_ZTVN10__cxxabiv117__class_type_infoE>;
> # SFT.5 = V_MAY_DEF <SFT.5>;
> # SFT.6 = V_MAY_DEF <SFT.6>;
> # SFT.7 = V_MAY_DEF <SFT.7>;
> # SFT.8 = V_MAY_DEF <SFT.8>;
> # SFT.9 = V_MAY_DEF <SFT.9>;
> # NONLOCAL.15 = V_MAY_DEF <NONLOCAL.15>;
> this_9->_vptr.basic_ostream = iftmp.1_13;
>
>
Uh, this is pretty weird.
*all* of these should have been marked for renaming, not just NONLOCAL.
next prev parent reply other threads:[~2006-10-25 12:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-24 19:12 [Bug tree-optimization/29585] New: [4.3 " tbm at cyrius dot com
2006-10-24 19:12 ` [Bug tree-optimization/29585] " tbm at cyrius dot com
2006-10-25 4:55 ` pinskia at gcc dot gnu dot org
2006-10-25 5:08 ` [Bug tree-optimization/29585] [4.2/4.3 " pinskia at gcc dot gnu dot org
2006-10-25 5:09 ` pinskia at gcc dot gnu dot org
2006-10-25 5:23 ` pinskia at gcc dot gnu dot org
2006-10-25 12:12 ` Daniel Berlin [this message]
2006-10-25 12:12 ` dberlin at dberlin dot org
2006-11-20 16:22 ` rguenth at gcc dot gnu dot org
2006-11-20 17:20 ` pinskia at gcc dot gnu dot org
2006-11-25 10:11 ` pinskia at gcc dot gnu dot org
2006-12-28 23:50 ` [Bug tree-optimization/29585] [4.2 " pinskia at gcc dot gnu dot org
2007-02-01 16:46 ` rguenth at gcc dot gnu dot org
2007-02-05 9:55 ` tbm at cyrius dot com
2007-02-19 13:07 ` rguenth at gcc dot gnu dot org
2007-02-19 20:36 ` mmitchel at gcc dot gnu dot org
2007-03-13 16:16 ` dnovillo at gcc dot gnu dot org
2007-03-29 18:55 ` dnovillo at gcc dot gnu dot org
2007-03-31 18:22 ` dnovillo at gcc dot gnu dot org
2007-03-31 18:28 ` dnovillo at gcc dot gnu dot org
2007-04-05 1:52 ` mrs at apple dot com
2007-04-13 2:09 ` mrs at apple dot com
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=4aca3dc20610250512x511a971bi9042db32e38ec43f@mail.gmail.com \
--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).