Bug 1400585 - internal compiler error: in output_constructor_regular_field, at varasm.c:4968
Summary: internal compiler error: in output_constructor_regular_field, at varasm.c:4968
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc
Version: 26
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-01 14:37 UTC by Ralf Corsepius
Modified: 2018-05-29 11:29 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-29 11:29:45 UTC
Type: Bug


Attachments (Terms of Use)
Preprocessed sources of this ICE (1.47 KB, text/x-csrc)
2016-12-01 14:37 UTC, Ralf Corsepius
no flags Details


Links
System ID Private Priority Status Summary Last Updated
GNU Compiler Collection 78635 0 P2 RESOLVED [6/7 Regression] internal compiler error: in output_constructor_regular_field, at varasm.c:4989 2020-02-23 22:51:53 UTC

Description Ralf Corsepius 2016-12-01 14:37:03 UTC
Created attachment 1226838 [details]
Preprocessed sources of this ICE

Description of problem:

g++ ICEs when compiling this code snippet:

# cat foo.cc
struct dirs_t {
  int	   x;
  char     y[];
};

struct dirs_t a[2] = { { 1, 'a' }, { 1, 'b' } };


# g++ -o foo -c foo.cc
foo.cc:6:48: internal compiler error: in output_constructor_regular_field, at varasm.c:4968
 struct dirs_t a[2] = { { 1, 'a' }, { 1, 'b' } };
                                                ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugzilla.redhat.com/bugzilla> for instructions.
Preprocessed source stored into /tmp/ccsv0S6O.out file, please attach this to your bugreport.



Version-Release number of selected component (if applicable):
gcc-c++-6.2.1-2.fc25.x86_64


How reproducible:
Always

Steps to Reproduce:
1. g++ -o foo foo.cc

Actual results:
ICE

Expected results:
Proper diagnosis.

Comment 1 Jonathan Wakely 2016-12-01 15:37:56 UTC
Reported upstream as https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78635

Comment 2 Fedora End Of Life 2017-11-16 19:19:20 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Ralf Corsepius 2017-11-18 11:53:30 UTC
Reopening.

Bug still unfixed in gcc-7.2.1-2.fc26.x86_64

Comment 4 Fedora End Of Life 2018-05-03 08:17:20 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2018-05-29 11:29:45 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.