From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: Jerry D <jvdelisle2@gmail.com>
Cc: "Jorge D'Elia" <jdelia@cimec.unl.edu.ar>,
Gfortran List <fortran@gcc.gnu.org>,
"Jorge D'Elia" <jdelia@intec.unl.edu.ar>
Subject: Re: beta gfortran 14.x.y (using -march=native and intrinsic repeat) gives a signal SIGILL
Date: Sat, 12 Aug 2023 07:56:44 +0100 [thread overview]
Message-ID: <CAGkQGiL=BHKnna2vf4qxWpTQuhruXDd1OvdCmY8-8=JhmkiDOw@mail.gmail.com> (raw)
In-Reply-To: <aac7dcb1-7fa6-7a09-447c-19e8f2cde6e5@gmail.com>
Hi Jorge,
> There were some recent patches in this area IIRC.
>
> Jerry
The tree dump is identical to mine, obtained with GNU Fortran (GCC)
14.0.0 20230809 (experimental), so I doubt that any recent patches are
responsible.
Being unable to reproduce the error, there is not much that I can do.
Sorry
Paul
next prev parent reply other threads:[~2023-08-12 6:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 12:34 Jorge D'Elia
2023-08-11 16:21 ` Jerry D
2023-08-11 16:55 ` Paul Richard Thomas
2023-08-11 17:42 ` Jorge D'Elia
2023-08-12 6:56 ` Paul Richard Thomas [this message]
2023-08-12 13:41 ` Jorge D'Elia
2023-08-12 16:05 ` Steve Kargl
2023-08-12 17:21 ` Jerry D
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='CAGkQGiL=BHKnna2vf4qxWpTQuhruXDd1OvdCmY8-8=JhmkiDOw@mail.gmail.com' \
--to=paul.richard.thomas@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=jdelia@cimec.unl.edu.ar \
--cc=jdelia@intec.unl.edu.ar \
--cc=jvdelisle2@gmail.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).