From: Jonathan Wakely <jwakely@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: "haochen.jiang" <haochenj@ecsmtp.sh.intel.com>,
Patrick Palka <ppalka@redhat.com>,
"jason@redhat.com" <jason@redhat.com>,
"gcc-regression@gcc.gnu.org" <gcc-regression@gcc.gnu.org>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"haochen.jiang@intel.com" <haochen.jiang@intel.com>
Subject: Re: [r14-159 Regression] FAIL: std/ranges/iota/max_size_type.cc execution test on Linux/x86_64
Date: Sun, 23 Apr 2023 00:26:38 +0100 [thread overview]
Message-ID: <CACb0b4mkK5A0LGLLkUs4p1WGeXuKnOkWz2k7W+v6utDn9DKdMQ@mail.gmail.com> (raw)
In-Reply-To: <ZEOQT9BbItFVgHG7@tucnak>
[-- Attachment #1: Type: text/plain, Size: 966 bytes --]
On Saturday, April 22, 2023, Jakub Jelinek <jakub@redhat.com> wrote:
> On Sat, Apr 22, 2023 at 11:30:24AM +0800, haochen.jiang via Gcc-patches
wrote:
>> On Linux/x86_64,
>>
>> 03cebd304955a6b9c5607e09312d77f1307cc98e is the first bad commit
>> commit 03cebd304955a6b9c5607e09312d77f1307cc98e
>> Author: Jason Merrill <jason@redhat.com>
>> Date: Tue Apr 18 21:32:07 2023 -0400
>>
>> c++: fix 'unsigned typedef-name' extension [PR108099]
>>
>> caused
>>
>> FAIL: std/ranges/iota/max_size_type.cc execution test
>
> That is mentioned in
> https://gcc.gnu.org/pipermail/gcc-patches/2023-April/616439.html
> as known problem. I think the test should use std::make_signed<rep_t>
> instead of signed rep_t
It's already testing non-public implementation details, it could just use
#if and use signed __int128 or signed long long as appropriate.
> which it uses, but as Jason mentioned,
> it reveals further problems that need to be looked at.
>
> Jakub
>
>
next prev parent reply other threads:[~2023-04-22 23:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-22 3:30 haochen.jiang
2023-04-22 7:44 ` Jakub Jelinek
2023-04-22 23:26 ` Jonathan Wakely [this message]
2023-04-24 16:27 ` Patrick Palka
2023-04-24 16:30 ` Jonathan Wakely
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=CACb0b4mkK5A0LGLLkUs4p1WGeXuKnOkWz2k7W+v6utDn9DKdMQ@mail.gmail.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc-regression@gcc.gnu.org \
--cc=haochen.jiang@intel.com \
--cc=haochenj@ecsmtp.sh.intel.com \
--cc=jakub@redhat.com \
--cc=jason@redhat.com \
--cc=ppalka@redhat.com \
/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).