public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/114819] New: 'constructor', 'destructor' function attributes vs. function signature Date: Tue, 23 Apr 2024 06:30:40 +0000 [thread overview] Message-ID: <bug-114819-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114819 Bug ID: 114819 Summary: 'constructor', 'destructor' function attributes vs. function signature Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: diagnostic, documentation Severity: minor Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: tschwinge at gcc dot gnu.org Target Milestone: --- In context of PR114818 "'constructor', 'destructor' function attributes vs. 'extern'", I also found that there's no user documentation that the constructor, destructor function signature has to match 'void FN(void)', and GCC currently doesn't check/diagnose this. Should we update 'gcc/doc/extend.texi' for this, and implement a diagnostic (warning or even error, enabled by default)? I found that we only document in 'gcc/target.def': /* Output a constructor for a symbol with a given priority. */ DEFHOOK (constructor, "If defined, a function that outputs assembler code to arrange to call\n\ the function referenced by @var{symbol} at initialization time.\n\ \n\ Assume that @var{symbol} is a @code{SYMBOL_REF} for a function taking\n\ no arguments and with no return value. [...] Note "a function taking no arguments and with no return value".
next reply other threads:[~2024-04-23 6:30 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-23 6:30 tschwinge at gcc dot gnu.org [this message] 2024-04-23 6:37 ` [Bug c/114819] " pinskia at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-114819-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).