public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at physics dot uc dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/11503] [3.3/3.4 Regression] segfault when instantiating template with ADDR_EXPR
Date: Fri, 11 Jul 2003 19:19:00 -0000	[thread overview]
Message-ID: <20030711191907.20593.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030711191311.11503.zlomek@gcc.gnu.org>

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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


pinskia at physics dot uc dot edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |critical
           Priority|P2                          |P1
            Summary|segfault when instantiating |[3.3/3.4 Regression]
                   |template with ADDR_EXPR     |segfault when instantiating
                   |                            |template with ADDR_EXPR
   Target Milestone|3.4                         |3.3.1


------- Additional Comments From pinskia at physics dot uc dot edu  2003-07-11 19:19 -------
Please do not confirm your own bug so that if you got something wrong there can be some peer 
review.

But this is a regression from 3.2.3, where it did not ICE.
On the mainline (20030711) and 3.3.1 (20030707), I do get the ICE.
Here part of the 3.4 backtrace:
#0  0x0812f402 in lookup_base (t=0x400b472c, base=0x400b472c, access=ba_check, 
kind_ptr=0x0) at /home/gates/pinskia/src/gnu/gcc/src/gcc/cp/search.c:311
#1  0x08114826 in build_unary_op (code=ADDR_EXPR, xarg=0x400bbaa0, 
noconvert=1074431140) at /home/gates/pinskia/src/gnu/gcc/src/gcc/cp/typeck.c:4246
#2  0x0804f811 in build_this (obj=0x64) at /home/gates/pinskia/src/gnu/gcc/src/gcc/cp/
call.c:2290
#3  0x08057275 in build_new_method_call (instance=0x400557f8, fns=0x40055810, args=0x0, 
conversion_path=0x0, flags=3) at /home/gates/pinskia/src/gnu/gcc/src/gcc/cp/call.c:4919
#4  0x080ad4aa in tsubst_copy_and_build (t=0x40055408, args=0x400b6794, complain=3, 
in_decl=0x400b0ec4) at /home/gates/pinskia/src/gnu/gcc/src/gcc/cp/pt.c:8201
#5  0x080a8c86 in tsubst_expr (t=0x400add0c, args=0x400b6794, complain=3, 
in_decl=0x400b0ec4) at /home/gates/pinskia/src/gnu/gcc/src/gcc/cp/pt.c:7595
#6  0x080a8bff in tsubst_expr (t=0x400adce4, args=0x400b6794, complain=3, 
in_decl=0x400b0ec4) at /home/gates/pinskia/src/gnu/gcc/src/gcc/cp/pt.c:7744
#7  0x080a8bff in tsubst_expr (t=0x400adcd0, args=0x400b6794, complain=3, 
in_decl=0x400b0ec4) at /home/gates/pinskia/src/gnu/gcc/src/gcc/cp/pt.c:7744
#8  0x080b697f in instantiate_decl (d=0x400b8d14, defer_ok=0) at /home/gates/pinskia/src/
gnu/gcc/src/gcc/cp/pt.c:11005
#9  0x080e4e75 in mark_used (decl=0x400b8d14) at /home/gates/pinskia/src/gnu/gcc/src/gcc/
cp/decl2.c:4248
#10 0x080556db in build_over_call (cand=0x400b265c, flags=3) at /home/gates/pinskia/src/
gnu/gcc/src/gcc/cp/call.c:4587
#11 0x080578a9 in build_new_method_call (instance=0x400adf28, fns=0x400b8d14, args=0x0, 
conversion_path=0x400aad80, flags=3) at /home/gates/pinskia/src/gnu/gcc/src/gcc/cp/
call.c:5077
#12 0x080f6c8f in cp_parser_postfix_expression (parser=0x400aa540, address_p=false) at /
home/gates/pinskia/src/gnu/gcc/src/gcc/cp/parser.c:3857
#13 0x080f7590 in cp_parser_unary_expression (parser=0x400aa540, address_p=false) at /
home/gates/pinskia/src/gnu/gcc/src/gcc/cp/parser.c:4363
#14 0x08101b79 in cp_parser_simple_cast_expression (parser=0x64) at /home/gates/pinskia/
src/gnu/gcc/src/gcc/cp/parser.c:13918
#15 0x08101212 in cp_parser_binary_expression (parser=0x400aa540, 
token_tree_map=0x849d2dc, fn=0x8101b60 <cp_parser_simple_cast_expression>)
    at /home/gates/pinskia/src/gnu/gcc/src/gcc/cp/parser.c:13436
#16 0x080f7f01 in cp_parser_pm_expression (parser=0x64) at /home/gates/pinskia/src/gnu/
gcc/src/gcc/cp/parser.c:4818
...


  parent reply	other threads:[~2003-07-11 19:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-11 19:13 [Bug c++/11503] New: " zlomek at gcc dot gnu dot org
2003-07-11 19:14 ` [Bug c++/11503] " zlomek at gcc dot gnu dot org
2003-07-11 19:19 ` pinskia at physics dot uc dot edu [this message]
2003-07-11 19:23 ` [Bug c++/11503] [3.3/3.4 Regression] " pinskia at physics dot uc dot edu
2003-07-11 19:24 ` pinskia at physics dot uc dot edu
2003-07-11 20:44 ` bangerth at dealii dot org
2003-07-12 14:12 ` s dot bosscher at student dot tudelft dot nl
2003-07-14  5:13 ` cvs-commit at gcc dot gnu dot org
2003-07-14  5:18 ` cvs-commit at gcc dot gnu dot org
2003-07-14  5:20 ` cvs-commit at gcc dot gnu dot org
2003-07-14  5:21 ` mmitchel 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=20030711191907.20593.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).