From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mgamail.intel.com (mgamail.intel.com [134.134.136.100]) by sourceware.org (Postfix) with ESMTPS id C43FE386480E; Thu, 21 Dec 2023 21:07:19 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org C43FE386480E Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=ecsmtp.sh.intel.com Authentication-Results: sourceware.org; spf=none smtp.mailfrom=ecsmtp.sh.intel.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org C43FE386480E Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=134.134.136.100 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1703192841; cv=none; b=dXKnKEBU55YnHn3ju0aAjW7oyEjyvVyalaf7LaqlvZ+F4KmV9Ye/qTwSO2x/coCyEQ2Dvrap0Kc2pKj+hFngQZOfedLBlDRCSgGuI1w1RPzA4RB+NFyNwRnqaFH3PgSFv45c51rVYHjr+SA/Umwwv1zA4JEYk4U81R72zqWYLn8= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1703192841; c=relaxed/simple; bh=TwzO0EEVn9dpUY/WCvrWkg0gCbVZtgjnef1ih3xtQBg=; h=From:Message-Id:Date:To:Subject; b=QDu1Ewfw81sBJnGo3OP+ycrp/iZoDnP+WoslUHF7k3CXoQGsFiajaso3wMD15a8gmCRVwHEOsoUjvgip8AIOdHNpMs3x4eIJgoD/W3PJr75lKKpBcKVV1m1Q/mcP4SRVdSEcMHfmfIkqzXNn37MphDhjbgzeMGhg7y47cuHHycs= ARC-Authentication-Results: i=1; server2.sourceware.org X-IronPort-AV: E=McAfee;i="6600,9927,10931"; a="462476757" X-IronPort-AV: E=Sophos;i="6.04,294,1695711600"; d="scan'208";a="462476757" Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Dec 2023 13:07:17 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10931"; a="895233634" X-IronPort-AV: E=Sophos;i="6.04,294,1695711600"; d="scan'208";a="895233634" Received: from shvmail03.sh.intel.com ([10.239.245.20]) by fmsmga002.fm.intel.com with ESMTP; 21 Dec 2023 13:07:14 -0800 Received: from shliclel4214.sh.intel.com (shliclel4214.sh.intel.com [10.239.240.214]) by shvmail03.sh.intel.com (Postfix) with ESMTP id A10F410056F3; Fri, 22 Dec 2023 05:07:13 +0800 (CST) Received: from shliclel4214.sh.intel.com (localhost [127.0.0.1]) by shliclel4214.sh.intel.com (8.16.1/8.12.8/MailSET/client) with ESMTP id 3BLL7CNi2366877; Fri, 22 Dec 2023 05:07:12 +0800 Received: (from haochenj@localhost) by shliclel4214.sh.intel.com (8.16.1/8.16.1/Submit) id 3BLL7BkC2366876; Fri, 22 Dec 2023 05:07:11 +0800 From: "haochen.jiang" Message-Id: <202312212107.3BLL7BkC2366876@shliclel4214.sh.intel.com> Date: Fri, 22 Dec 2023 05:07:11 +0800 To: uecker@tugraz.at, gcc-regression@gcc.gnu.org, gcc-patches@gcc.gnu.org, haochen.jiang@intel.com Subject: [r14-6770 Regression] FAIL: gcc.dg/gnu23-tag-4.c (test for excess errors) on Linux/x86_64 User-Agent: s-nail v14.9.22 X-Spam-Status: No, score=-0.5 required=5.0 tests=BAYES_00,KAM_DMARC_STATUS,KAM_LAZY_DOMAIN_SECURITY,KAM_NUMSUBJECT,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: On Linux/x86_64, 23fee88f84873b0b8b41c8e5a9b229d533fb4022 is the first bad commit commit 23fee88f84873b0b8b41c8e5a9b229d533fb4022 Author: Martin Uecker Date: Tue Aug 15 14:58:32 2023 +0200 c23: tag compatibility rules for struct and unions caused FAIL: gcc.dg/gnu23-tag-4.c (test for excess errors) with GCC configured with ../../gcc/configure --prefix=/export/users/haochenj/src/gcc-bisect/master/master/r14-6770/usr --enable-clocale=gnu --with-system-zlib --with-demangler-in-ld --with-fpmath=sse --enable-languages=c,c++,fortran --enable-cet --without-isl --enable-libmpx x86_64-linux --disable-bootstrap To reproduce: $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/gnu23-tag-4.c --target_board='unix{-m32\ -march=cascadelake}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/gnu23-tag-4.c --target_board='unix{-m64\ -march=cascadelake}'" (Please do not reply to this email, for question about this report, contact me at haochen dot jiang at intel.com.) (If you met problems with cascadelake related, disabling AVX512F in command line might save that.) (However, please make sure that there is no potential problems with AVX512.)