internal compiler error: in build_zero_init_1, at cp/init.c:279

Bug #1093055 reported by Adam Seering
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gcc
Fix Released
Medium
gcc-4.6 (Ubuntu)
Triaged
Medium
Unassigned
gcc-4.7 (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

I'm running the latest version of the gcc/g++ packages for Ubuntu 12.04:

$ g++ --version
g++ (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3
Copyright (C) 2011 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

$ apt-cache policy g++-4.6
g++-4.6:
  Installed: 4.6.3-1ubuntu5
  Candidate: 4.6.3-1ubuntu5
  Version table:
 *** 4.6.3-1ubuntu5 0
        500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status

$ lsb_release -rd
Description: Ubuntu 12.04.1 LTS
Release: 12.04

I'm trying to compile a particular source file. When I compile it as follows, I get the following error:

$ g++ -I ../include -I HelperLibraries -g -Wall -Wno-unused-value -shared -fPIC -o build/BasicIntegerParser_continuous.so ParserFunctions/BasicIntegerParser_continuous.cpp ../include/Vertica.cpp
ParserFunctions/BasicIntegerParser_continuous.cpp: In member function ‘virtual Vertica::UDParser* BasicIntegerParserFactory::prepare(Vertica::ServerInterface&, Vertica::PerColumnParamReader&, Vertica::PlanContext&, const Vertica::SizedColumnTypes&)’:
ParserFunctions/BasicIntegerParser_continuous.cpp:76:16: internal compiler error: in build_zero_init_1, at cp/init.c:279
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.6/README.Bugs> for instructions.
Preprocessed source stored into /tmp/cc8HZt1y.out file, please attach this to your bugreport.

I expected the file to compile properly, or at least provide an error message describing a fault in my code rather than in the compiler.

I have attached the preprocessed source file as requested by the error message.

Please let me know if I can help out in debugging or fixing.

Revision history for this message
Adam Seering (aseering) wrote :
Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

Confirmed this on 4.6.3-13ubuntu1 on raring.

Changed in gcc-4.6 (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

Also triggered on 4.7.2-16ubuntu1 on raring:

$ g++-4.7 cc8HZt1y.i
ParserFunctions/BasicIntegerParser_continuous.cpp: In member function ‘virtual Vertica::UDParser* BasicIntegerParserFactory::prepare(Vertica::ServerInterface&, Vertica::PerColumnParamReader&, Vertica::PlanContext&, const Vertica::SizedColumnTypes&)’:
ParserFunctions/BasicIntegerParser_continuous.cpp:76:103: internal compiler error: in build_zero_init_1, at cp/init.c:280
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.7/README.Bugs> for instructions.
Preprocessed source stored into /tmp/ccFMAgK5.out file, please attach this to your bugreport.

Changed in gcc-4.7 (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Adam Seering (aseering) wrote :

For what it's worth, I've also reproduced this on RHEL 6: "Red Hat 4.4.5-6"

It does not reproduce on RHEL 5 ("Red Hat 4.1.2-52").

I assume this is an upstream bug. I don't see it in the upstream bugtracker. Do any gcc maintainers lurk here?; should I re-file this upstream or is it useful to have it here?

Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

Probably useful to file upstream; please provide the links for the upstream tracker if you do.

Revision history for this message
Adam Seering (aseering) wrote :

I've posted this bug upstream: <http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56403>

Revision history for this message
Adam Seering (aseering) wrote :

This bug has been fixed in upstream SVN for gcc 4.6, 4.7, and trunk (4.8).

Could the upstream fix be pulled in? (Will it automatically be pulled in the next time upstream posts a new minor-version release for these versions?)

Changed in gcc-4.7 (Ubuntu):
status: Confirmed → Triaged
Changed in gcc-4.6 (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Matthias Klose (doko) wrote :

fixed in 4.7.2-22ubuntu4

Changed in gcc-4.7 (Ubuntu):
status: Triaged → Fix Released
Changed in gcc:
importance: Unknown → Medium
status: Unknown → Fix Released
Revision history for this message
Adam Seering (aseering) wrote :

Thanks for the 4.7 fix!

Would it be possible to pull in the 4.6 patch as well? I believe the change is equivalent; it has likewise been backported upstream already.

Revision history for this message
Adam Seering (aseering) wrote :

Just checking back in: What's the process for getting this sort of patch applied? Is there anything I can do to help?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.