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/104352] ICE in gfc_conv_intrinsic_anyall, at fortran/trans-intrinsic.cc:4481 (etc.)
Date: Wed, 02 Feb 2022 18:50:11 +0000	[thread overview]
Message-ID: <bug-104352-4-AgSw0VSm9N@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104352-4@http.gcc.gnu.org/bugzilla/>

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

G. Steinmetz <gscfq@t-online.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |ice-on-invalid-code

--- Comment #1 from G. Steinmetz <gscfq@t-online.de> ---

Intrinsic "any" in above test files can be replaced with e.g.

$ cat za1.f90
program p
   integer, parameter :: a(0) = 1
   print *, all(a(1:1) == 1)
   print *, any(a(1:1) == 1)
   print *, count(a(1:1) == 1)
   print *, is_contiguous(a(1:1) == 1)
   print *, parity(a(1:1) == 1)
   print *, shape(a(1:1) == 1)
   print *, size(a(1:1) == 1)
   print *, ubound(a(1:1) == 1)
end


Other variants also affect intrinsics like iany, iall, ...

$ cat zb1.f90
program p
   integer, parameter :: a(0) = 1
   print *, iall(a(1:1))
   print *, iany(a(1:1))
   print *, iparity(a(1:1))
   print *, maxval(a(1:1))
   print *, minval(a(1:1))
   print *, product(a(1:1))
   print *, sum(a(1:1))
end


Another modification pattern hits minloc, macloc, ...

$ cat zc1.f90
program p
   integer, parameter :: a(0) = 1
   print *, ibclr(a(1:1), 1)
   print *, ibset(a(1:1), 1)
   print *, max(a(1:1), 1)
   print *, max0(a(1:1), 1)
   print *, maxloc(a(1:1), 1)
   print *, min(a(1:1), 1)
   print *, min0(a(1:1), 1)
   print *, minloc(a(1:1), 1)
end


or ...

$ cat zd1.f90
program p
   real, parameter :: a(0) = 1
   print *, dot_product(a(1:1), a(1:1))
   print *, norm2(a(1:1))
end
subroutine s
   complex, parameter :: a(0) = 1
   print *, dot_product(a(1:1), a(1:1))
   print *, conjg(a(1:1))
end

  reply	other threads:[~2022-02-02 18:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-02 18:48 [Bug fortran/104352] New: " gscfq@t-online.de
2022-02-02 18:50 ` gscfq@t-online.de [this message]
2022-05-25 20:37 ` [Bug fortran/104352] " kargl at gcc dot gnu.org
2022-10-21 20:18 ` anlauf at gcc dot gnu.org
2023-05-17 19:56 ` cvs-commit at gcc dot gnu.org
2023-05-17 20:00 ` anlauf at gcc dot gnu.org
2024-04-02 17:07 ` cvs-commit 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-104352-4-AgSw0VSm9N@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).