https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71463
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71463
--- Comment #16 from Milian Wolff ---
So how can I silence the warning then for the case I pasted in the first
comment:
~~~+
#include
template struct foo {};
foo emit_unexpected_warning;
int main() { return
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71463
--- Comment #15 from Martin Sebor ---
As Jason explained it works as designed. But the warning is certainly
confusing. It doesn't help that not all attributes enjoy this special
treatment or that the manual doesn't explain it. At a minimum, I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71463
--- Comment #14 from Jakub Jelinek ---
> I imagine it was to support using them on function pointers.
Yes, that is the reason why they apply to function types rather than decls.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71463
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71463
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|6.3 |6.4
--- Comment #12 from Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71463
--- Comment #11 from Richard Biener ---
GCC 6.2 is being released, adjusting target milestone.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71463
Richard Biener changed:
What|Removed |Added
Target Milestone|6.2 |6.3
--- Comment #10 from Richard
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71463
--- Comment #9 from Jason Merrill ---
(In reply to Milian Wolff from comment #8)
> As an interested bystander, may I ask: If the attribute is part of the type,
> shouldn't it then be transferred via decltype() and then also used in the
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71463
--- Comment #8 from Milian Wolff ---
As an interested bystander, may I ask: If the attribute is part of the type,
shouldn't it then be transferred via decltype() and then also used in the
template to trigger the warning there? To me, the example
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71463
--- Comment #7 from Jason Merrill ---
(In reply to Martin Sebor from comment #6)
> I didn't know that GCC considers attribute warn_unused_result part of the
> function type. When you say that most of these attributes apply to the
> function
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71463
--- Comment #6 from Martin Sebor ---
I didn't know that GCC considers attribute warn_unused_result part of the
function type. When you say that most of these attributes apply to the
function type, which others are you referring to?
FWIW, I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71463
Jason Merrill changed:
What|Removed |Added
CC||jason at gcc dot gnu.org
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71463
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71463
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |6.2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71463
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Known to work|
16 matches
Mail list logo