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++/108099] ICE when parsing signed __int128_t typedef Date: Wed, 14 Dec 2022 12:23:54 +0000 [thread overview] Message-ID: <bug-108099-4-NiTbtJ6rmy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108099-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108099 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Keywords| |ice-on-invalid-code Last reconfirmed| |2022-12-14 Status|UNCONFIRMED |NEW --- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Jonathan Wakely from comment #1) > __int128_t is already a typedef, so you can't add a signed or unsigned > qualifier to it. i.e. the same reason this doesn't work: using I = int; signed I i = 0; > std::make_signed_t<__int128_t> works because that doesn't just add the > 'signed' keyword to it. i.e. the same reason this works: using I = int; std::make_signed_t<I> i = 0; It shouldn't ICE though.
next prev parent reply other threads:[~2022-12-14 12:23 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-14 11:52 [Bug c++/108099] New: " moritz.klammler at cetitec dot com 2022-12-14 12:20 ` [Bug c++/108099] " redi at gcc dot gnu.org 2022-12-14 12:23 ` redi at gcc dot gnu.org [this message] 2022-12-14 12:26 ` redi at gcc dot gnu.org 2022-12-14 13:12 ` moritz.klammler at cetitec dot com 2022-12-14 17:46 ` [Bug c++/108099] ICE with type alias with `signed __int_128_t` pinskia at gcc dot gnu.org 2022-12-14 17:54 ` [Bug c++/108099] ICE with type alias with `signed __int128_t` pinskia at gcc dot gnu.org 2022-12-14 17:58 ` [Bug c++/108099] [12/13 Regression] " pinskia at gcc dot gnu.org 2022-12-14 18:18 ` jakub at gcc dot gnu.org 2022-12-14 19:05 ` jakub at gcc dot gnu.org 2022-12-14 19:20 ` jakub at gcc dot gnu.org 2022-12-21 12:37 ` rguenth at gcc dot gnu.org 2022-12-21 18:14 ` ville.voutilainen at gmail dot com 2023-01-31 16:00 ` pinskia at gcc dot gnu.org 2023-02-01 0:51 ` pinskia at gcc dot gnu.org 2023-02-01 11:59 ` redi at gcc dot gnu.org 2023-02-01 19:07 ` pinskia at gcc dot gnu.org 2023-02-01 19:17 ` jakub at gcc dot gnu.org 2023-03-09 22:25 ` jason at gcc dot gnu.org 2023-03-10 3:57 ` cvs-commit at gcc dot gnu.org 2023-03-10 3:59 ` [Bug c++/108099] [12 " jason at gcc dot gnu.org 2023-03-10 10:33 ` jakub at gcc dot gnu.org 2023-04-18 20:45 ` cvs-commit at gcc dot gnu.org 2023-04-19 15:23 ` cvs-commit at gcc dot gnu.org 2023-04-19 16:53 ` cvs-commit at gcc dot gnu.org 2023-04-19 16:59 ` [Bug c++/108099] [12/13/14 " jason at gcc dot gnu.org 2023-04-20 7:44 ` cvs-commit at gcc dot gnu.org 2023-04-20 7:48 ` cvs-commit at gcc dot gnu.org 2023-04-21 19:33 ` cvs-commit at gcc dot gnu.org 2023-05-02 20:25 ` [Bug c++/108099] [12/13 " cvs-commit at gcc dot gnu.org 2023-05-08 12:26 ` rguenth at gcc dot gnu.org 2023-07-25 10:50 ` [Bug c++/108099] [12 " redi at gcc dot gnu.org 2023-08-11 21:21 ` cvs-commit at gcc dot gnu.org 2023-12-19 21:50 ` jason 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-108099-4-NiTbtJ6rmy@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).