This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/56403] [4.6/4.7 Regression] internal compiler error: in build_zero_init_1, at cp/init.c:279
- From: "manu at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 14 Mar 2013 15:43:28 +0000
- Subject: [Bug c++/56403] [4.6/4.7 Regression] internal compiler error: in build_zero_init_1, at cp/init.c:279
- Auto-submitted: auto-generated
- References: <bug-56403-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56403
Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |patch
CC| |manu at gcc dot gnu.org
--- Comment #12 from Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> 2013-03-14 15:43:28 UTC ---
(In reply to comment #11)
> I'm not familiar with gcc's backport process; is there anything I can do to
> help that along? Is it already in-queue?
I guess Jakub is extremely busy with the imminent release of GCC 4.8.0.
To backport, someone would need to apply the patch here:
http://gcc.gnu.org/r196260 to the GCC 4.7 branch here:
http://gcc.gnu.org/svn/gcc/branches/gcc-4_7-branch/ then bootstrap + regression
test and check if there are any new failures. Then submit the patch with an
appropriate changelog to gcc-patches. Since the patch is already written, I
don't think you need a copyright assignment to do any of this.