From: Jakub Jelinek <jakub@redhat.com>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, fortran <fortran@gcc.gnu.org>
Subject: Re: [Patch] Fortran/OpenMP: Avoid ICE for invalid char array in omp atomic [PR104329]
Date: Wed, 9 Feb 2022 20:27:03 +0100 [thread overview]
Message-ID: <20220209192703.GU2646553@tucnak> (raw)
In-Reply-To: <21a15d76-bc78-5cfc-bdf1-9839e3dcedf0@codesourcery.com>
On Fri, Feb 04, 2022 at 12:39:53PM +0100, Tobias Burnus wrote:
> Already during parsing, the allocatable character array assignment
> x = (x)
>
> is converted to two gfc_codes with EXEC_ASSIGN, namely:
>
> ASSIGN z1:_F.DA0(FULL) (parens z1:x(FULL))
> ASSIGN z1:x(FULL) z1:_F.DA0(FULL)
>
> But the current code expects only one gfc_code - as parse.c does some
> checks, that's unexpected for resolution and currently is checked with
> an gcc_assert.
>
> Solution: I now defer the gfc_assert until after diagnosing the arguments.
>
> OK for mainline (only affected version)?
>
> Tobias
> -----------------
> Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
> Fortran/OpenMP: Avoid ICE for invalid char array in omp atomic [PR104329]
>
> PR fortran/104329
> gcc/fortran/ChangeLog:
>
> * openmp.cc (resolve_omp_atomic): Defer extra-code assert after
> other diagnostics.
>
> gcc/testsuite/ChangeLog:
>
> * gfortran.dg/gomp/atomic-28.f90: New test.
>
> gcc/fortran/openmp.cc | 11 ++++++++---
> gcc/testsuite/gfortran.dg/gomp/atomic-28.f90 | 28 ++++++++++++++++++++++++++++
> 2 files changed, 36 insertions(+), 3 deletions(-)
Ok, thanks.
Jakub
prev parent reply other threads:[~2022-02-09 19:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 11:39 Tobias Burnus
2022-02-09 19:27 ` Jakub Jelinek [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=20220209192703.GU2646553@tucnak \
--to=jakub@redhat.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=tobias@codesourcery.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).