[Bug c++/81837] Internal compiler error (cp/typeck2.c:1264)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81837 --- Comment #10 from Paolo Carlini --- In my opinion we should *always* set it when closing bugs: many, many, users complain that isn't always clear which is the first release where a bug is fixed. Actually, we should also spend more time on keeping up to date the "Known to work" and "Known to fail" fields.
[Bug c++/81837] Internal compiler error (cp/typeck2.c:1264)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81837 --- Comment #9 from Eric Gallager --- (In reply to Paolo Carlini from comment #8) > In any case, please always set the Target Milestone when closing a bug. I thought that was just for regressions...
[Bug c++/81837] Internal compiler error (cp/typeck2.c:1264)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81837 Paolo Carlini changed: What|Removed |Added Target Milestone|--- |8.0 --- Comment #8 from Paolo Carlini --- In any case, please always set the Target Milestone when closing a bug.
[Bug c++/81837] Internal compiler error (cp/typeck2.c:1264)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81837
Eric Gallager changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
CC||egallager at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #7 from Eric Gallager ---
(In reply to Vegard Nossum from comment #5)
> This looks like it has been fixed, maybe somebody can confirm and change
> status.
Output is now:
$ /usr/local/bin/g++ -c -std=c++14 -g -Wall -Wextra 81837.cc
81837.cc: In function 'int main()':
81837.cc:18:42: error: name 'align' used in a GNU-style designated initializer
for an array
chunk = new Unit [10] {.align = 0};
^
81837.cc:18:42: error: could not convert '0' from 'int' to 'Unit'
$
So confirmed that there's no more ICE. I think the 2 remaining errors are
different enough so as not to need to be de-duplicated, but feel free to open a
new bug if you think there should only be one.
[Bug c++/81837] Internal compiler error (cp/typeck2.c:1264)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81837 --- Comment #6 from Paolo Carlini --- See Comment 4: why 2 errors?
[Bug c++/81837] Internal compiler error (cp/typeck2.c:1264)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81837 vegard.nossum at gmail dot com changed: What|Removed |Added CC||vegard.nossum at oracle dot com --- Comment #5 from vegard.nossum at gmail dot com --- This looks like it has been fixed, maybe somebody can confirm and change status.
[Bug c++/81837] Internal compiler error (cp/typeck2.c:1264)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81837 Paolo Carlini changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |paolo.carlini at oracle dot com --- Comment #4 from Paolo Carlini --- My patch for PR82593 essentially fixed this one too, but I think we can avoid some redundant diagnostics.
[Bug c++/81837] Internal compiler error (cp/typeck2.c:1264)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81837 Martin Liška changed: What|Removed |Added Keywords||ice-on-invalid-code Status|UNCONFIRMED |NEW Last reconfirmed||2017-08-16 CC||marxin at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #3 from Martin Liška --- Confirmed, all releases ICE.
[Bug c++/81837] Internal compiler error (cp/typeck2.c:1264)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81837 --- Comment #2 from Eric Gallager --- *** Bug 81839 has been marked as a duplicate of this bug. ***
[Bug c++/81837] Internal compiler error (cp/typeck2.c:1264)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81837 --- Comment #1 from Eric Gallager --- *** Bug 81838 has been marked as a duplicate of this bug. ***
