public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/19311] [3.4/4.0/4.1 Regression] ICE in resolve_overloaded_unification
Date: Sat, 05 Mar 2005 15:44:00 -0000 [thread overview]
Message-ID: <20050305154437.8701.qmail@sourceware.org> (raw)
In-Reply-To: <20050107131252.19311.jakub@gcc.gnu.org>
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-03-05 15:44 -------
Subject: Bug 19311
CVSROOT: /cvs/gcc
Module name: gcc
Changes by: lerdsuwa@gcc.gnu.org 2005-03-05 15:44:26
Modified files:
gcc/cp : init.c pt.c typeck.c ChangeLog
gcc/testsuite : ChangeLog
Added files:
gcc/testsuite/g++.dg/template: non-dependent11.C
Log message:
PR c++/19311
* init.c (build_offset_ref): Don't build non-dependent SCOPE_REF.
* pt.c (build_non_dependent_expr): Don't build NON_DEPENDENT_EXPR
for OFFSET_TYPE.
* typeck.c (build_x_unary_op): Don't build non-dependent SCOPE_REF.
Also set PTRMEM_OK_P for NON_DEPENDENT_EXPR.
(build_unary_op): Handle building ADDR_EXPR of OFFSET_REF inside
template.
* g++.dg/template/non-dependent11.C: New test.
Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/cp/init.c.diff?cvsroot=gcc&r1=1.412&r2=1.413
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/cp/pt.c.diff?cvsroot=gcc&r1=1.978&r2=1.979
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/cp/typeck.c.diff?cvsroot=gcc&r1=1.616&r2=1.617
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/cp/ChangeLog.diff?cvsroot=gcc&r1=1.4652&r2=1.4653
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/template/non-dependent11.C.diff?cvsroot=gcc&r1=NONE&r2=1.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/ChangeLog.diff?cvsroot=gcc&r1=1.5112&r2=1.5113
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19311
next prev parent reply other threads:[~2005-03-05 15:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 13:13 [Bug c++/19311] New: " jakub at gcc dot gnu dot org
2005-01-07 13:46 ` [Bug c++/19311] [3.4/4.0 Regression] " pinskia at gcc dot gnu dot org
2005-01-07 14:02 ` pinskia at gcc dot gnu dot org
2005-01-07 20:58 ` bangerth at dealii dot org
2005-01-08 22:52 ` pinskia at gcc dot gnu dot org
2005-01-10 0:50 ` pinskia at gcc dot gnu dot org
2005-01-10 14:11 ` lerdsuwa at gcc dot gnu dot org
2005-01-12 10:49 ` lerdsuwa at gcc dot gnu dot org
2005-01-13 6:07 ` lerdsuwa at gcc dot gnu dot org
2005-01-17 14:37 ` lerdsuwa at gcc dot gnu dot org
2005-01-17 15:32 ` giovannibajo at libero dot it
2005-01-17 16:19 ` lerdsuwa at gcc dot gnu dot org
2005-02-01 15:04 ` caolanm at redhat dot com
2005-03-01 0:09 ` [Bug c++/19311] [3.4/4.0/4.1 " pinskia at gcc dot gnu dot org
2005-03-02 0:08 ` giovannibajo at libero dot it
2005-03-04 2:17 ` mmitchel at gcc dot gnu dot org
2005-03-05 15:44 ` cvs-commit at gcc dot gnu dot org [this message]
2005-03-05 15:46 ` [Bug c++/19311] [3.4/4.0 " lerdsuwa at gcc dot gnu dot org
2005-03-06 16:59 ` cvs-commit at gcc dot gnu dot org
2005-03-06 17:12 ` cvs-commit at gcc dot gnu dot org
2005-03-06 17:16 ` lerdsuwa 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=20050305154437.8701.qmail@sourceware.org \
--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).