public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/108450] New: [12/13 Regression] ICE in sort_actual, at fortran/intrinsic.cc:4380
Date: Wed, 18 Jan 2023 18:23:03 +0000	[thread overview]
Message-ID: <bug-108450-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108450

            Bug ID: 108450
           Summary: [12/13 Regression] ICE in sort_actual, at
                    fortran/intrinsic.cc:4380
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

Started between 20211128 and 20211205 :


$ cat z1.f90
program p
   integer :: a(8) = 0
   integer :: l
   integer :: n
   !$omp atomic
   n = maxloc(a, mask=l)
end


$ cat z2.f90
program p
   integer :: a(8) = 0
   logical :: l
   integer :: n(1)
   !$omp atomic
   n = maxloc(a, mask=l)
end


$ gfortran-13-20230115 -c z2.f90 -fopenmp
z2.f90:6:3:

    6 |    n = maxloc(a, mask=l)
      |   1
Error: !$OMP ATOMIC statement must set a scalar variable of intrinsic type at
(1)


$ gfortran-13-20230115 -c z1.f90 -fopenmp
z1.f90:6:22:

    6 |    n = maxloc(a, mask=l)
      |                      1
Error: 'mask' argument of 'maxloc' intrinsic at (1) must be LOGICAL
f951: internal compiler error: Segmentation fault
0xf8734f crash_signal
        ../../gcc/toplev.cc:314
0x84f083 sort_actual
        ../../gcc/fortran/intrinsic.cc:4380
0x84f2d4 check_specific
        ../../gcc/fortran/intrinsic.cc:4774
0x8574c4 gfc_intrinsic_func_interface(gfc_expr*, int)
        ../../gcc/fortran/intrinsic.cc:5042
0x8aeb18 resolve_unknown_f
        ../../gcc/fortran/resolve.cc:2990
0x8aeb18 resolve_function
        ../../gcc/fortran/resolve.cc:3347
0x8aeb18 gfc_resolve_expr(gfc_expr*)
        ../../gcc/fortran/resolve.cc:7195
0x8806a4 resolve_omp_atomic
        ../../gcc/fortran/openmp.cc:8699
0x88de6c gfc_resolve_omp_directive(gfc_code*, gfc_namespace*)
        ../../gcc/fortran/openmp.cc:10190
0x8b48ab gfc_resolve_code(gfc_code*, gfc_namespace*)
        ../../gcc/fortran/resolve.cc:12444
0x8b69e7 resolve_codes
        ../../gcc/fortran/resolve.cc:17629
0x8b6aae gfc_resolve(gfc_namespace*)
        ../../gcc/fortran/resolve.cc:17664
0x89e844 resolve_all_program_units
        ../../gcc/fortran/parse.cc:6656
0x89e844 gfc_parse_file()
        ../../gcc/fortran/parse.cc:6912
0x8ed3af gfc_be_parse_file
        ../../gcc/fortran/f95-lang.cc:229

             reply	other threads:[~2023-01-18 18:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18 18:23 gscfq@t-online.de [this message]
2023-01-19  7:47 ` [Bug fortran/108450] " rguenth at gcc dot gnu.org
2023-01-19 14:16 ` [Bug fortran/108450] [12/13 Regression] ICE in sort_actual, at fortran/intrinsic.cc:4380 since r12-5793-g689407ef916503b2 marxin at gcc dot gnu.org
2023-01-20 18:03 ` burnus at gcc dot gnu.org
2023-01-29 19:47 ` mikael at gcc dot gnu.org
2023-01-29 20:57 ` cvs-commit at gcc dot gnu.org
2023-02-05 21:53 ` cvs-commit at gcc dot gnu.org
2023-02-05 22:22 ` mikael at gcc dot gnu.org

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=bug-108450-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).