From: Harald Anlauf <anlauf@gmx.de>
To: fortran <fortran@gcc.gnu.org>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: *PING* [PATCH] Fortran: incorrect array bounds when bound intrinsic used in decl [PR108131]
Date: Fri, 23 Dec 2022 17:14:24 +0100 [thread overview]
Message-ID: <d76db47e-4733-0c82-2f4d-b0ebcd97f586@gmx.de> (raw)
In-Reply-To: <trinity-3d8a6fbe-9e01-4e21-960b-3fde6a9d9f51-1671312077244@3c-app-gmx-bap49>
Am 17.12.22 um 22:21 schrieb Harald Anlauf via Gcc-patches:
> Dear all,
>
> the previous fix for pr103505 introduced a regression that could lead
> to wrong array bounds when LBOUND/UBOUND were used in the array spec
> of a declaration. The reason was that we tried to simplify too early
> the array element spec, which appears to have interfered with the
> subtle semantics of the bound intrinsics.
>
> The solution is to undo the fix for pr103505. It turns out that
> there are other code changes in place that were put in place to
> fix related ICEs, and which handle that one, too, and only lead
> to a change of the emitted error diagnostics.
>
> Regtested on x86_64-pc-linux-gnu. OK for mainline?
>
> As this is a 10/11/12/13 regression, I would like to backport
> as seems fit.
>
> Thanks,
> Harald
>
next prev parent reply other threads:[~2022-12-23 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-17 21:21 Harald Anlauf
2022-12-23 16:14 ` Harald Anlauf [this message]
2022-12-23 21:12 ` 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=d76db47e-4733-0c82-2f4d-b0ebcd97f586@gmx.de \
--to=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@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).