public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mserdarsanli at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/108613] [12/13 Regression] GCC12 internal compiler error on __int128_t in type_traits header
Date: Wed, 01 Feb 2023 22:03:47 +0000 [thread overview]
Message-ID: <bug-108613-4-7pXnaflDjQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108613-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108613
--- Comment #6 from Serdar Sanli <mserdarsanli at gmail dot com> ---
> Where did you get this from? The <type_traits> header uses signed __int128 here, not signed __int128_t.
Just checked and __GLIBCXX_TYPE_INT_N_0 is also __int128 for me. int128_t seem
to come from somewhere else, in my case it is in cuda compiler generated code.
Sorry for not being clear and wasting time, snippet I copied was only intended
as a repro, not as a bug report on stdlibc++.
next prev parent reply other threads:[~2023-02-01 22:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 12:07 [Bug c++/108613] New: " mserdarsanli at gmail dot com
2023-01-31 15:00 ` [Bug c++/108613] [12/13 Regression] " rguenth at gcc dot gnu.org
2023-01-31 15:39 ` ppalka at gcc dot gnu.org
2023-01-31 15:59 ` pinskia at gcc dot gnu.org
2023-01-31 16:00 ` pinskia at gcc dot gnu.org
2023-02-01 19:52 ` redi at gcc dot gnu.org
2023-02-01 22:03 ` mserdarsanli at gmail dot com [this message]
2023-02-01 22:40 ` redi 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-108613-4-7pXnaflDjQ@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).