public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/9452: [2003-05-03] ICE (segfault) using a dependent expression as argument for the template-id in the return type
Date: Fri, 16 May 2003 20:06:00 -0000 [thread overview]
Message-ID: <20030516200601.3271.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/9452; it has been noted by GNATS.
From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: Giovanni Bajo <giovannibajo@libero.it>
Cc: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org>,
Gabriel Dos Reis <gdr@integrable-solutions.net>
Subject: Re: c++/9452: [2003-05-03] ICE (segfault) using a dependent expression
as argument for the template-id in the return type
Date: Fri, 16 May 2003 15:02:12 -0500 (CDT)
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9452
>
> I think the segfault happens while trying to format the error message.
No, that's not the case. The error happens here (this is present mainline):
#0 convert_from_reference (val=0x40159528)
at ../../gcc-3.4-CVS/gcc/cp/cvt.c:557
#1 0x08052c35 in prep_operand (operand=0x40159528)
at ../../gcc-3.4-CVS/gcc/cp/call.c:3561
#2 0x08052f79 in build_new_op (code=MINUS_EXPR, flags=3, arg1=0x40159528,
arg2=0x401a0f28, arg3=0x0) at ../../gcc-3.4-CVS/gcc/cp/call.c:3662
#3 0x081143f6 in build_x_binary_op (code=MINUS_EXPR, arg1=0x40159528,
arg2=0x0) at ../../gcc-3.4-CVS/gcc/cp/typeck.c:2947
#4 0x0809e635 in tsubst_template_arg_vector (t=0x401a0f50, args=0x40159510,
complain=tf_none) at ../../gcc-3.4-CVS/gcc/cp/pt.c:5676
#5 0x0809ed80 in tsubst_aggr_type (t=0x401aabd0, args=0x40159510,
complain=tf_none, in_decl=0x0, entering_scope=0)
at ../../gcc-3.4-CVS/gcc/cp/pt.c:5794
#6 0x080a2d7c in tsubst (t=0x401aac3c, args=0x40159510, complain=tf_none,
in_decl=0x0) at ../../gcc-3.4-CVS/gcc/cp/pt.c:6578
#7 0x080a1f34 in tsubst_function_type (t=0x401aac3c, args=0x40159510,
complain=tf_none, in_decl=0x401aabd0) at ../../gcc-3.4-CVS/gcc/cp/pt.c:6445
#8 0x080a30e8 in tsubst (t=0x401ad000, args=0x40159510, complain=tf_none,
in_decl=0x0) at ../../gcc-3.4-CVS/gcc/cp/pt.c:6960
#9 0x080aedbd in fn_type_unification (fn=0x401ad0d8, explicit_targs=0x0,
targs=0x401ad000, args=0x401ac7bc, return_type=0x0, strict=DEDUCE_CALL,
len=-1) at ../../gcc-3.4-CVS/gcc/cp/pt.c:8649
The place in convert_reference is this:
tree
convert_from_reference (tree val)
{
tree type = TREE_TYPE (val);
if (TREE_CODE (type) == OFFSET_TYPE) -------- here
type = TREE_TYPE (type);
if (TREE_CODE (type) == REFERENCE_TYPE)
return build_indirect_ref (val, NULL);
return val;
}
and the reason is that type==0x0. Now, as to why that is happening...
W.
-------------------------------------------------------------------------
Wolfgang Bangerth email: bangerth@ices.utexas.edu
www: http://www.ices.utexas.edu/~bangerth/
next reply other threads:[~2003-05-16 20:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-16 20:06 Wolfgang Bangerth [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-16 17:26 Giovanni Bajo
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=20030516200601.3271.qmail@sources.redhat.com \
--to=bangerth@ices.utexas.edu \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).