public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "luigighiron at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/114808] Qualified void return type is not diagnosed
Date: Mon, 22 Apr 2024 19:42:55 +0000	[thread overview]
Message-ID: <bug-114808-4-0ZiXHmgeRr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114808-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114808

--- Comment #5 from Halalaluyafail3 <luigighiron at gmail dot com> ---
I made this bug report because of the warning that clang has, but the following
paragraph may allow this:

> If, in the declaration "T D1", D1 has the form
> D ( parameter-type-list )
> or
> D ( identifier-list opt )
> and the type specified for ident in the declaration "T D" is
> "derived-declarator-type-list T", then the type specified for
> ident is "derived-declarator-type-list function returning the
> unqualified version of T".
Section 6.7.6.3 "Function declarators (including prototypes)" Paragraph 4
ISO/IEC 9899:2018

GCC seems to be using this to not make a diagnostic here, e.g. it warns with a
return type of _Atomic void in C17 mode but not in C23 mode where the text here
was updated to indicate that the result is the unqualified and non-atomic
version of T. If this would make the text talking about the return type of the
function refer to the unqualified return type then this should be allowed I
think, and I will make a bug report to clang to get this diagnostic changed.

  parent reply	other threads:[~2024-04-22 19:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22 17:02 [Bug c/114808] New: " luigighiron at gmail dot com
2024-04-22 19:11 ` [Bug c/114808] " jakub at gcc dot gnu.org
2024-04-22 19:15 ` pinskia at gcc dot gnu.org
2024-04-22 19:17 ` jakub at gcc dot gnu.org
2024-04-22 19:34 ` pinskia at gcc dot gnu.org
2024-04-22 19:42 ` luigighiron at gmail dot com [this message]
2024-04-22 19:46 ` luigighiron at gmail dot com
2024-04-22 19:54 ` jsm28 at gcc dot gnu.org
2024-04-22 20:11 ` pinskia at gcc dot gnu.org
2024-04-23  1:12 ` luigighiron at gmail dot com
2024-04-23  5:54 ` xry111 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-114808-4-0ZiXHmgeRr@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: link
Be 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).