public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <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 10:36:32 +0000	[thread overview]
Message-ID: <bug-84764-4-0RXSql9fAK@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

--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Daniel Lundin from comment #3)
> gcc behaves just like required too, since `__int128` ought to be one of the
> extended integer types and it is signed.

But it's not an extended integer type, see comment 2.

I think that will change for C23, which allows intmax_t to be be defined to
long long even if there are larger extended integer types. But in GCC today,
there are no extended integer types.

  parent reply	other threads:[~2023-01-25 10:36 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
2023-01-25 10:36 ` redi at gcc dot gnu.org [this message]
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-0RXSql9fAK@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).