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++/12218] [3.4 regression] runtime segfault when initializing global variable with pointer-to-member
Date: Wed, 17 Dec 2003 04:55:00 -0000	[thread overview]
Message-ID: <20031217044602.31866.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030908222714.12218.bryner@brianryner.com>


------- Additional Comments From cvs-commit at gcc dot gnu dot org  2003-12-17 04:46 -------
Subject: Bug 12218

CVSROOT:	/cvs/gcc
Module name:	gcc
Changes by:	mmitchel@gcc.gnu.org	2003-12-17 04:45:53

Modified files:
	gcc            : ChangeLog varasm.c 
	gcc/cp         : ChangeLog decl.c 
	gcc/testsuite  : ChangeLog 
Added files:
	gcc/testsuite/g++.dg/init: error1.C pm3.C 

Log message:
	PR c++/12218
	* varasm.c (initializer_constant_valid_p): Allow a conversion from
	an integral constant to an OFFSET_TYPE.
	
	PR c++/12696
	* decl.c (reshape_init): Recover quickly from errors.
	
	PR c++/12218
	* g++.dg/init/pm3.C: New test.
	
	PR c++/12696
	* g++.dg/init/error1.C: New test.

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&r1=2.2014&r2=2.2015
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/varasm.c.diff?cvsroot=gcc&r1=1.399&r2=1.400
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/cp/ChangeLog.diff?cvsroot=gcc&r1=1.3814&r2=1.3815
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/cp/decl.c.diff?cvsroot=gcc&r1=1.1162&r2=1.1163
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/ChangeLog.diff?cvsroot=gcc&r1=1.3273&r2=1.3274
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/init/error1.C.diff?cvsroot=gcc&r1=NONE&r2=1.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/init/pm3.C.diff?cvsroot=gcc&r1=NONE&r2=1.1



-- 


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


  parent reply	other threads:[~2003-12-17  4:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-08 22:27 [Bug c++/12218] New: code generated for initializing global variable with pointer-to-member crashes bryner at brianryner dot com
2003-09-08 22:29 ` [Bug c++/12218] " bryner at brianryner dot com
2003-09-08 22:30 ` bryner at brianryner dot com
2003-09-08 23:14 ` [Bug c++/12218] [3.4 regression] runtime segfault when initializing global variable with pointer-to-member bangerth at dealii dot org
2003-09-08 23:18 ` pinskia at gcc dot gnu dot org
2003-09-08 23:20 ` bryner at brianryner dot com
2003-09-08 23:22 ` bangerth at dealii dot org
2003-09-08 23:27 ` bangerth at dealii dot org
2003-09-08 23:39 ` dbaron at dbaron dot org
2003-09-08 23:49 ` dbaron at dbaron dot org
2003-09-09 21:58 ` dbaron at dbaron dot org
2003-09-11 18:37 ` dbaron at dbaron dot org
2003-09-15  7:07 ` dbaron at dbaron dot org
2003-09-16 21:56 ` bangerth at dealii dot org
2003-10-06 23:26 ` dbaron at dbaron dot org
2003-10-14 21:07 ` pinskia at gcc dot gnu dot org
2003-11-14 22:21 ` pinskia at gcc dot gnu dot org
2003-12-02  0:48 ` zack at gcc dot gnu dot org
2003-12-02  1:30 ` bangerth at dealii dot org
2003-12-17  2:28 ` mmitchel at gcc dot gnu dot org
2003-12-17  4:55 ` cvs-commit at gcc dot gnu dot org [this message]
2003-12-17  5:36 ` 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=20031217044602.31866.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).