[Bug c++/84360] unnecessary aka in error message
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84360 Jonathan Wakely changed: What|Removed |Added Target Milestone|9.5 |---
[Bug c++/84360] unnecessary aka in error message
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84360 Richard Biener changed: What|Removed |Added Target Milestone|9.4 |9.5 --- Comment #9 from Richard Biener --- GCC 9.4 is being released, retargeting bugs to GCC 9.5.
[Bug c++/84360] unnecessary aka in error message
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84360 Jakub Jelinek changed: What|Removed |Added Target Milestone|9.3 |9.4 --- Comment #8 from Jakub Jelinek --- GCC 9.3.0 has been released, adjusting target milestone.
[Bug c++/84360] unnecessary aka in error message
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84360 Jakub Jelinek changed: What|Removed |Added Target Milestone|9.2 |9.3 --- Comment #7 from Jakub Jelinek --- GCC 9.2 has been released.
[Bug c++/84360] unnecessary aka in error message
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84360 Jakub Jelinek changed: What|Removed |Added Target Milestone|9.0 |9.2 --- Comment #6 from Jakub Jelinek --- GCC 9.1 has been released.
[Bug c++/84360] unnecessary aka in error message
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84360
Eric Gallager changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed||2018-06-17
CC||egallager at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #5 from Eric Gallager ---
(In reply to Jonathan Wakely from comment #4)
> (In reply to David Malcolm from comment #3)
> > So should this ideally read:
> > return type ‘T’ {aka ‘class std::tuple’} is incomplete
> > to express both the name the code used, and the underlying type?
>
> Yes.
Confirming and changing status to ASSIGNED since David put himself as the
assignee.
[Bug c++/84360] unnecessary aka in error message
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84360 David Malcolm changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |dmalcolm at gcc dot gnu.org Target Milestone|--- |9.0
[Bug c++/84360] unnecessary aka in error message
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84360
--- Comment #4 from Jonathan Wakely ---
(In reply to David Malcolm from comment #3)
> So should this ideally read:
> return type ‘T’ {aka ‘class std::tuple’} is incomplete
> to express both the name the code used, and the underlying type?
Yes.
[Bug c++/84360] unnecessary aka in error message
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84360
--- Comment #3 from David Malcolm ---
As I understand it, "using" is a more modern form of typedef (e.g. with
template support).
So should this ideally read:
return type ‘T’ {aka ‘class std::tuple’} is incomplete
to express both the name the code used, and the underlying type?
[Bug c++/84360] unnecessary aka in error message
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84360 Jakub Jelinek changed: What|Removed |Added CC||dmalcolm at gcc dot gnu.org, ||jason at gcc dot gnu.org, ||redi at gcc dot gnu.org --- Comment #2 from Jakub Jelinek --- I wonder if we can just do a textual hack like also checking if p + type_start starts with "using " and p + type_start + type_len - aka_len memcmps equal to p + aka_start and p + type_start + type_len - aka_len - 3 is " = ", or if we need to do something harder, like duplicating parts of dump_type and dump_decl and checking for the using case.
[Bug c++/84360] unnecessary aka in error message
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84360 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #1 from Jakub Jelinek --- cp/error.c has code to avoid printing aka same as the first type: /* If they are identical, cut off the aka by unwinding the obstack. */ if (type_len == aka_len && memcmp (p + type_start, p+aka_start, type_len) == 0) but that doesn't trigger in this case, because p + type_start with type_len length is "using T = class std::tuple" and p + aka_start with aka_len is just: "class std::tuple"
