Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 525442 - Internal compiler error: Error reporting routines re-entered.
Summary: Internal compiler error: Error reporting routines re-entered.
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GCC Porting (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-14 20:50 UTC by Petr Hudecek
Modified: 2014-10-16 07:31 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
Truth.cpp (Truth.cpp,3.64 KB, text/plain)
2014-10-14 20:50 UTC, Petr Hudecek
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Hudecek 2014-10-14 20:50:49 UTC
Created attachment 386692 [details]
Truth.cpp

When compiling the attached file by

"g++ -std=c++1 ~/Truth.cpp -o /tmp/truth.exe"

the compiler outputted:

"Internal compiler error: Error reporting routines re-entered.
Please submit a full bug report."
Comment 1 Rafał Mużyło 2014-10-14 23:29:02 UTC
This is something that needs to be reported to *gcc* upstream.

Though I suspect a part of your problem is https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54316, as the program bails upon 'chunks.push_back(novyStream);' line, which seems to be a workaround for non-working 'chunks.emplace_back' line.
Comment 2 Jeroen Roovers (RETIRED) gentoo-dev 2014-10-15 07:56:39 UTC
1) Please post your `emerge --info' output in a comment.
2) Please post your `gcc-config -l' output in a comment.
3) Please post the complete output of the command, without quotation marks or editing.
Comment 3 Rafał Mużyło 2014-10-15 15:39:17 UTC
The only typo in that command is the obvious one '-std=c++11'.
It's reproducible with gcc 4.7.4 - not sure about later versions (as the upstream bug says, emplace_back problem will be fixed in gcc 5, not sure about this compiler error though).
Comment 4 Petr Hudecek 2014-10-15 16:40:57 UTC
This error occurs at 4.7.4.

In 4.9.1, it prints the correct error messages.
Comment 5 Rafał Mużyło 2014-10-15 18:19:24 UTC
(In reply to Petr Hudecek from comment #4)
> This error occurs at 4.7.4.
> 
> In 4.9.1, it prints the correct error messages.

Well, in such case, upstream would most likely mark it as WONTFIX (definitely, if it's fixed on 4.8 too).