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.133.124]) by sourceware.org (Postfix) with ESMTPS id AE4BA3858D28 for ; Tue, 5 Sep 2023 21:52:23 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org AE4BA3858D28 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=1693950743; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=w92CcETUnD23J/R7bhj3mKQcYl0vZh1W6D6odeYMohk=; b=DLfzqcRbLN+GrWQYc+5UYM/YxJkooH8S0eQAGKczWGolpw7WugW+Lgwf4LgyVDK+dMfaZk VgNsPXdfnuRJ1mUozEXu/el1dPho249xpwXQRqLHQA7ik8v2Nnmw343260ZbdX31pLiQDs STH0donhLecktUEBZrmOngrackOSa44= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-482-h0emFyfoMmiUGBMPMLqwMQ-1; Tue, 05 Sep 2023 17:52:22 -0400 X-MC-Unique: h0emFyfoMmiUGBMPMLqwMQ-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 9E47D181BBC3; Tue, 5 Sep 2023 21:52:21 +0000 (UTC) Received: from tucnak.zalov.cz (unknown [10.45.224.16]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 637242026D4B; Tue, 5 Sep 2023 21:52:21 +0000 (UTC) Received: from tucnak.zalov.cz (localhost [127.0.0.1]) by tucnak.zalov.cz (8.17.1/8.17.1) with ESMTPS id 385LqJqZ1746484 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Tue, 5 Sep 2023 23:52:19 +0200 Received: (from jakub@localhost) by tucnak.zalov.cz (8.17.1/8.17.1/Submit) id 385LqJle1746483; Tue, 5 Sep 2023 23:52:19 +0200 Date: Tue, 5 Sep 2023 23:52:19 +0200 From: Jakub Jelinek To: Andrew Pinski Cc: Richard Biener , gcc-patches@gcc.gnu.org Subject: Re: [PATCH 18/12] Handle BITINT_TYPE in build_{, minus_}one_cst [PR102989] Message-ID: Reply-To: Jakub Jelinek References: MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 3.1 on 10.11.54.4 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-3.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On Tue, Sep 05, 2023 at 02:42:39PM -0700, Andrew Pinski wrote: > On Tue, Sep 5, 2023 at 12:31 AM Jakub Jelinek via Gcc-patches > > Recent match.pd changes trigger ICE in build_minus_one_cst, apparently > > I forgot to handle BITINT_TYPE in these (while I've handled it in > > build_zero_cst). > > > > Will commit as obvious together with the rest of the series when the last > > patches are approved. > > I assume there was a testcase that will be added when _BitInt > front-end support gets added. After working around the build_nonstandard_integer_type in match.pd (in that case the single one, I know there are some others) the ICE was on dg-torture/bitint-42.c at -O1/-Os, so no new testcase needs to be added. Jakub