From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 141A33858C50 for ; Sat, 22 Apr 2023 23:26:43 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 141A33858C50 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1682206002; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=QZ1mXZQO3H6Z3FMu++WqE3UYjDP0VFJeYbIHb4tRQC8=; b=Sj6uJ17k8K0MLekWjHgMzGT4qLqNNOZmpThlwd2638B6DDx6eC/o50zXmO8TpDkcg4P6y/ mXsncOIyhRruubwpusw9gvdI3Bol3dSzZoZQ7jESn1vGDblwBZtO8BHNGIe7GipikJa1lJ ORxO/pXxDLfXE7JEhdxnbQOTykI/njo= Received: from mail-lj1-f197.google.com (mail-lj1-f197.google.com [209.85.208.197]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-663-miWW1GoIPe6pVy6s5Mt87w-1; Sat, 22 Apr 2023 19:26:40 -0400 X-MC-Unique: miWW1GoIPe6pVy6s5Mt87w-1 Received: by mail-lj1-f197.google.com with SMTP id 38308e7fff4ca-2a83a0b7be1so12203311fa.1 for ; Sat, 22 Apr 2023 16:26:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682205999; x=1684797999; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=QZ1mXZQO3H6Z3FMu++WqE3UYjDP0VFJeYbIHb4tRQC8=; b=JjtRY0AS0YCCnuCE1dVK62LpgxTl+ppWxfZ+dV2RwdlQLBt9d0a//ujQCkKcJ87yL4 6ze4NVJn5+h2j50WKM9npAuqOvpPZ0VeTvZ9ZNqp31aePLCxuQzx2FsLhmoSy90AeXV9 SVUPj5YQS+HY0lFUZpNaPMuIowF2OrlLBy9M+D2HfTZpWcHty8OREaZDFT6FWSjApuuY 6Skpk4uct6/t/4SsAaqgflR5Htt+3Y47j8XvaNJ9IYFpC6WFpHjvFr+ykQTQ8Ys00A6G tVdMb8rA3jh6L1jmrVm2oFE+ubjHeB2cOBPFHFaBCnnbrXZVRvgdQhrrcNV428i16rWE fB9A== X-Gm-Message-State: AAQBX9fntm+O9WB95REvIypWCjLYAHW2PCGxK7ypW1iADALGWfcoHj2y C5wolLpUrId8KfrcmsOkj1RxCb8BoFrHNFVx8G7mUOucvu6UGcSx8LvKKAKeS/vufdG+IZx+Tki 5xYKewZtTJsmM8a/bWTdsxgZpQ9B23M+MAQ== X-Received: by 2002:a2e:2416:0:b0:2a8:b7c3:65f with SMTP id k22-20020a2e2416000000b002a8b7c3065fmr1578584ljk.4.1682205999330; Sat, 22 Apr 2023 16:26:39 -0700 (PDT) X-Google-Smtp-Source: AKy350ZA4ogwo423ys1P3510P8YAAVqxLEFgorWs5ce0ZFQgpPsJ+XspptbDQ9JFqQQ4TLBYaYR5n4dL+jogbAUvDbY= X-Received: by 2002:a2e:2416:0:b0:2a8:b7c3:65f with SMTP id k22-20020a2e2416000000b002a8b7c3065fmr1578579ljk.4.1682205998953; Sat, 22 Apr 2023 16:26:38 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a2e:8748:0:b0:2a8:e791:5f05 with HTTP; Sat, 22 Apr 2023 16:26:38 -0700 (PDT) In-Reply-To: References: <202304220330.33M3UOTu3169661@shliclel4214.sh.intel.com> From: Jonathan Wakely Date: Sun, 23 Apr 2023 00:26:38 +0100 Message-ID: Subject: Re: [r14-159 Regression] FAIL: std/ranges/iota/max_size_type.cc execution test on Linux/x86_64 To: Jakub Jelinek Cc: "haochen.jiang" , Patrick Palka , "jason@redhat.com" , "gcc-regression@gcc.gnu.org" , "gcc-patches@gcc.gnu.org" , "haochen.jiang@intel.com" X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: multipart/alternative; boundary="00000000000001cac905f9f51b99" X-Spam-Status: No, score=-6.0 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,HTML_MESSAGE,KAM_NUMSUBJECT,KAM_SHORT,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,TXREP,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: --00000000000001cac905f9f51b99 Content-Type: text/plain; charset="UTF-8" On Saturday, April 22, 2023, Jakub Jelinek 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 >> 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 > 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 > > --00000000000001cac905f9f51b99--