public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "daniel.lundin.mail at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/84764] Wrong warning "so large that it is unsigned" for __int128 constant Date: Wed, 25 Jan 2023 09:45:31 +0000 [thread overview] Message-ID: <bug-84764-4-yq06ijSXZt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-84764-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84764 Daniel Lundin <daniel.lundin.mail at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |daniel.lundin.mail at gmail dot co | |m --- Comment #3 from Daniel Lundin <daniel.lundin.mail at gmail dot com> --- This is a bug as in the wrong text is displayed in the diagnostic message. gcc picks `__int128` and it is not an unsigned type. Decimal integer constants use the the quoted list in 6.4.4.1: `int` then `long` then `long long`. Therefore this normative text (from C99 to C23) applies: "If all of the types in the list for the constant are signed, the extended integer type shall be signed." gcc behaves just like required too, since `__int128` ought to be one of the extended integer types and it is signed. I would guess this message is some remain from C90 where extended integer types didn't exist. Compiling with -std=c90 adds an additional warning "warning: this decimal constant is unsigned only in ISO C90". It would appear that this is the correct warning that should always be displayed. Seems to be a minor bug that occurred during the switch (gcc 5.0.0) from gnu90 to gnu11 as default option.
next parent reply other threads:[~2023-01-25 9:45 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-84764-4@http.gcc.gnu.org/bugzilla/> 2023-01-25 9:45 ` daniel.lundin.mail at gmail dot com [this message] 2023-01-25 10:36 ` redi at gcc dot gnu.org 2023-01-26 1:26 ` joseph at codesourcery dot com 2023-01-26 7:53 ` daniel.lundin.mail at gmail dot com
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-84764-4-yq06ijSXZt@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).