This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/68334] combination of weak and noreturn attributes
- From: "joseph at codesourcery dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 13 Nov 2015 13:57:02 +0000
- Subject: [Bug c/68334] combination of weak and noreturn attributes
- Auto-submitted: auto-generated
- References: <bug-68334-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68334
--- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
I don't see any difference between declaring the function noreturn (or
pure, or const, or returning non-aliased memory like malloc, or ...) and
declaring it to have a certain type. In both cases, if overriding at link
time is allowed, the overriding copy must still have the declared
property.