From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Federico Perini via Fortran <fortran@gcc.gnu.org>
Subject: Re: [Bug 106731] ICE on automatic array of derived type with DTIO: need help
Date: Fri, 16 Dec 2022 10:07:08 -0800 [thread overview]
Message-ID: <Y5yzzCGYZ8JyAYZm@troutmask.apl.washington.edu> (raw)
In-Reply-To: <CAEj9oJSAvQc-7NgTcZ7V9zuegU-03bgOJ_Nf6w9zd4wL_5mRqA@mail.gmail.com>
On Thu, Dec 15, 2022 at 01:51:26PM +0100, Federico Perini via Fortran wrote:
>
> 3. Of the optimization flags "-fpeel-loops" is the one that triggers the
> failing tests
>
> 3. in dtio_4.f90, the first test fails for 1) non-extended class; 2)
> derived-type READ. Write works; extended type (BT_CLASS) works. It appears
> that the optimizer thinks the derived type is not modified by the read
> statement.
Federico, thanks for following up here. As I indicated before,
you're in an area of the compiler that I do not normally hack. But,
the above description sounds like a tree is not marked as used.
There is code of the form "TREE_USED (decl) = 1;" in the trans-*.cc
files. Setting this might inhibit the -fpeel-loops optimization,
but this is just a guess.
--
Steve
prev parent reply other threads:[~2022-12-16 18:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 12:51 Federico Perini
2022-12-16 18:07 ` Steve Kargl [this message]
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=Y5yzzCGYZ8JyAYZm@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=fortran@gcc.gnu.org \
/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).