public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/9342: [3.3/3.4 regression] another ICE in cp_expr_size at cp/cp-lang.c: 304
Date: Thu, 16 Jan 2003 20:06:00 -0000 [thread overview]
Message-ID: <20030116200601.5770.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/9342; it has been noted by GNATS.
From: Janis Johnson <janis187@us.ibm.com>
To: jason@redhat.com, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, matz@suse.de,
gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org
Cc:
Subject: Re: c++/9342: [3.3/3.4 regression] another ICE in cp_expr_size at
cp/cp-lang.c: 304
Date: Thu, 16 Jan 2003 12:05:36 -0800
This regression showed up starting with this patch:
--- gcc/ChangeLog ---
2002-08-02 Jason Merrill <jason@redhat.com>
* langhooks-def.h (LANG_HOOKS_EXPR_SIZE): New macro.
* langhooks.c (lhd_expr_size): Define default.
* langhooks.h (struct lang_hooks): Add expr_size.
* explow.c (expr_size): Call it.
* expr.c (store_expr): Don't copy an expression of size zero.
(expand_expr) [CONSTRUCTOR]: Use expr_size to calculate how much
to store.
* Makefile.in (builtins.o): Depend on langhooks.h.
--- gcc/cp/ChangeLog ---
* cp-lang.c (LANG_HOOKS_EXPR_SIZE): Define.
(cp_expr_size): New fn.
* call.c (build_over_call): Lose empty class hackery.
(convert_arg_to_ellipsis): Promote non-POD warning to error.
* typeck.c (build_modify_expr): Don't use save_expr on an
lvalue.
The ICE can be reproduced on i686-linux with the reduced
test case.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9342
next reply other threads:[~2003-01-16 20:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 20:06 Janis Johnson [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-18 16:21 paolo
2003-01-16 15:22 bangerth
2003-01-16 14:36 matz
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=20030116200601.5770.qmail@sources.redhat.com \
--to=janis187@us.ibm.com \
--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).