public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/109453] UBOUND incorrect when used in declartion of another array
Date: Sun, 09 Apr 2023 00:31:00 +0000 [thread overview]
Message-ID: <bug-109453-4-p5k5rI3ZUY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109453-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109453
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu.org
--- Comment #1 from kargl at gcc dot gnu.org ---
Works for me.
gfcx -o z -O a.f90 -fcheck=all && ./z
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
0 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
1 21 19 -1
1 20 19 0
hotrats:kargl[321] valgrind ./z
==50637== Memcheck, a memory error detector
==50637== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==50637== Using Valgrind-3.20.0 and LibVEX; rerun with -h for copyright info
==50637== Command: ./z
==50637==
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
0 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
1 21 19 -1
1 20 19 0
==50637==
==50637== HEAP SUMMARY:
==50637== in use at exit: 0 bytes in 0 blocks
==50637== total heap usage: 20 allocs, 20 frees, 9,661 bytes allocated
==50637==
==50637== All heap blocks were freed -- no leaks are possible
==50637==
==50637== For lists of detected and suppressed errors, rerun with: -s
==50637== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
next prev parent reply other threads:[~2023-04-09 0:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-09 0:02 [Bug fortran/109453] New: " jvdelisle at gcc dot gnu.org
2023-04-09 0:31 ` kargl at gcc dot gnu.org [this message]
2023-04-09 0:33 ` [Bug fortran/109453] " kargl at gcc dot gnu.org
2023-04-09 1:25 ` [Bug fortran/109453] [REGRESSION] " jvdelisle at gcc dot gnu.org
2023-04-09 1:42 ` sgk at troutmask dot apl.washington.edu
2023-04-09 1:46 ` jvdelisle at gcc dot gnu.org
2023-04-09 2:16 ` jvdelisle 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-109453-4-p5k5rI3ZUY@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).