From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by sourceware.org (Postfix) with ESMTPS id 2B9243858D20 for ; Sat, 12 Aug 2023 16:05:38 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 2B9243858D20 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=troutmask.apl.washington.edu Authentication-Results: sourceware.org; spf=none smtp.mailfrom=troutmask.apl.washington.edu Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.17.1/8.17.1) with ESMTPS id 37CG5aNA055888 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sat, 12 Aug 2023 09:05:36 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.17.1/8.17.1/Submit) id 37CG5awL055887; Sat, 12 Aug 2023 09:05:36 -0700 (PDT) (envelope-from sgk) Date: Sat, 12 Aug 2023 09:05:36 -0700 From: Steve Kargl To: "Jorge D'Elia via Fortran" Cc: Paul Richard Thomas , "Jorge D'Elia" , Jerry Subject: Re: beta gfortran 14.x.y (using -march=native and intrinsic repeat) gives a signal SIGILL Message-ID: Reply-To: sgk@troutmask.apl.washington.edu References: <1302200217.1817.1691757297462.JavaMail.zimbra@intec.unl.edu.ar> <1762418863.818.1691847670663.JavaMail.zimbra@intec.unl.edu.ar> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1762418863.818.1691847670663.JavaMail.zimbra@intec.unl.edu.ar> X-Spam-Status: No, score=-1.6 required=5.0 tests=BAYES_00,KAM_DMARC_STATUS,KAM_LAZY_DOMAIN_SECURITY,SPF_HELO_NONE,SPF_NONE,TXREP 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 Sat, Aug 12, 2023 at 10:41:10AM -0300, Jorge D'Elia via Fortran wrote: > > $ test-march.exe > > Program received signal SIGILL: Illegal instruction. > This, to me, suggests that the backend is emitting a wrong assembly language code. I suspect that you'll need to compare the generated assembly code between a working gfortran and the bad gfortran. It is also possible to get a listing of the actually options that -march=native activates. For example, % gfcx -o z -O -march=native --verbose a.f90 It is the options that begin with -m that matter. For my hardware I see 108 such options. With patients you can determine if one of these triggers the issues. One can also scan gcc/gcc/ChangeLog for changes to config/i386/i386.md. For example 2023-08-07 Jan Beulich * config/i386/i386.md (sse4_1_round2): Make "length_immediate" uniformly 1. * config/i386/mmx.md (mmx_pblendvb_v8qi): Likewise. (mmx_pblendvb_): Likewise. There are at least 10 commits on 2023-08-07 to this file. Finally, as a non-git user, you can always try git's bisection feature to identify where things go left. -- Steve