[Bug c++/67767] -Wsuggest-attribute=noreturn suggests noreturn for function which already has noreturn and cold.

2016-02-17 Thread zerotype at yahoo dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67767 --- Comment #2 from zerotype at yahoo dot com --- This can be worked around by using: [[gnu::cold]] [[gnu::noreturn]] instead of [[gnu::cold, gnu::noreturn]]

[Bug c++/67767] New: -Wsuggest-attribute=noreturn suggests noreturn for function which already has noreturn and cold.

2015-09-29 Thread zerotype at yahoo dot com
Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: zerotype at yahoo dot com Target Milestone: --- (Observed in Ubuntu builds of g++ 4.9.2 and 5.1.0) I have a class containing various function pointers

[Bug c++/67767] -Wsuggest-attribute=noreturn suggests noreturn for function which already has noreturn and cold.

2015-09-29 Thread zerotype at yahoo dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67767 --- Comment #1 from zerotype at yahoo dot com --- This particular use case also challenges the assertion in the GCC documentation that "It does not make sense for a noreturn function to have a return type other than void.". Some of th

[Bug libstdc++/40856] numeric_limits not specialized for __int128_t or __uint128_t

2012-10-22 Thread zerotype at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40856 zerotype at yahoo dot com changed: What|Removed |Added CC||zerotype at yahoo dot