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++/13663] [3.3 Regression] g++ segfaults in cc1plus
Date: Tue, 13 Jan 2004 05:43:00 -0000	[thread overview]
Message-ID: <20040113054327.29878.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040112235903.13663.richard@garandnet.net>


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-01-13 05:43 -------
The problem is this backtrace:
#0  walk_tree (tp=0x449091f0, func=0x828b870 <copy_body_r>, data=0xbffeb6a0, htab_=0x0) 
at ../../gcc/tree-inline.c:1715
#1  0x0828cc43 in walk_tree (tp=0x449091b4, func=0x828b870 <copy_body_r>, 
data=0xbffeb6a0, htab_=0x0) at ../../gcc/tree-inline.c:1627
#2  0x0828cc43 in walk_tree (tp=0x44909098, func=0x828b870 <copy_body_r>, 
data=0xbffeb6a0, htab_=0x0) at ../../gcc/tree-inline.c:1627
#3  0x0828cc43 in walk_tree (tp=0x44908104, func=0x828b870 <copy_body_r>, 
data=0xbffeb6a0, htab_=0x0) at ../../gcc/tree-inline.c:1627
#4  0x0828cc43 in walk_tree (tp=0x44906340, func=0x828b870 <copy_body_r>, 
data=0xbffeb6a0, htab_=0x0) at ../../gcc/tree-inline.c:1627
#5  0x0828cc43 in walk_tree (tp=0xbffeb684, func=0x828b870 <copy_body_r>, 
data=0xbffeb6a0, htab_=0x0) at ../../gcc/tree-inline.c:1627
#6  0x0828bb57 in copy_body (id=0x3) at ../../gcc/tree-inline.c:591
#7  0x0828ca5e in clone_body (clone=0x44901e4c, fn=0x44905c00, arg_map=0x3) at ../../gcc/
tree-inline.c:1517
#8  0x080c5056 in maybe_clone_body (fn=0x447bda10) at ../../gcc/cp/optimize.c:259
#9  0x080bfc4f in expand_body (fn=0x447bda10) at ../../gcc/cp/semantics.c:2328
#10 0x0809c568 in yyparse () at parse.y:2257
#11 0x080dba19 in c_common_parse_file (set_yydebug=3) at ../../gcc/c-lex.c:159
#12 0x0827e54a in compile_file () at ../../gcc/toplev.c:2130
#13 0x082837c5 in do_compile () at ../../gcc/toplev.c:5384
#14 0x08283859 in toplev_main (argc=3, argv=0x0) at ../../gcc/toplev.c:5414
#15 0x080e1cfb in main (argc=3, argv=0x3) at ../../gcc/main.c:35

I can confirm this on 3.3.3 but works right on the mainline (after normal tweaks to the source for 
the libstdc++ headers).

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1
           Keywords|                            |ice-on-valid-code
   Last reconfirmed|0000-00-00 00:00:00         |2004-01-13 05:43:23
               date|                            |
            Summary|g++ segfaults in cc1plus    |[3.3 Regression] g++
                   |                            |segfaults in cc1plus
   Target Milestone|---                         |3.3.3


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


  parent reply	other threads:[~2004-01-13  5:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-12 23:59 [Bug c++/13663] New: " richard at garandnet dot net
2004-01-13  0:00 ` [Bug c++/13663] " richard at garandnet dot net
2004-01-13  5:43 ` pinskia at gcc dot gnu dot org [this message]
2004-01-15 15:23 ` [Bug c++/13663] [3.3 Regression] " bangerth at dealii dot org
2004-01-23 21:29 ` [Bug c++/13663] [3.3/3.4/3.5 regression] gcc segfaults on/accepts invalid use of member reichelt at gcc dot gnu dot org
2004-01-26 14:25 ` bangerth at dealii dot org
2004-01-26 19:13 ` mmitchel at gcc dot gnu dot org
2004-01-26 20:12 ` cvs-commit at gcc dot gnu dot org
2004-01-26 20:13 ` cvs-commit at gcc dot gnu dot org
2004-01-26 20:13 ` cvs-commit at gcc dot gnu dot org
2004-01-26 20:15 ` [Bug c++/13663] [3.3 " mmitchel at gcc dot gnu dot org
2004-02-15 12:39 ` [Bug c++/13663] [3.3 regression] gcc segfaults on " gdr at gcc dot gnu dot org
2004-03-13  1:10 ` gdr at gcc dot gnu dot org
2004-03-30 19:11 ` pinskia at gcc dot gnu dot org
2004-04-27  6:44 ` gdr 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=20040113054327.29878.qmail@sources.redhat.com \
    --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).