public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/109453] [REGRESSION] UBOUND incorrect when used in declartion of another array Date: Sun, 09 Apr 2023 01:25:16 +0000 [thread overview] Message-ID: <bug-109453-4-18WvapdNP8@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 Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|UBOUND incorrect when used |[REGRESSION] UBOUND |in declartion of another |incorrect when used in |array |declartion of another array --- Comment #3 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> --- I am using: $ gfc -v Using built-in specs. COLLECT_GCC=gfc COLLECT_LTO_WRAPPER=/home/jerry/dev/usr/libexec/gcc/x86_64-pc-linux-gnu/13.0.1/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: ../trunk/configure --prefix=/home/jerry/dev/usr --enable-languages=c,c++,fortran --enable-libgomp --disable-bootstrap Thread model: posix Supported LTO compression algorithms: zlib gcc version 13.0.1 20230407 (experimental) (GCC) So that makes this a regression I believe.
next prev parent reply other threads:[~2023-04-09 1:25 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 ` [Bug fortran/109453] " kargl at gcc dot gnu.org 2023-04-09 0:33 ` kargl at gcc dot gnu.org 2023-04-09 1:25 ` jvdelisle at gcc dot gnu.org [this message] 2023-04-09 1:42 ` [Bug fortran/109453] [REGRESSION] " 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-18WvapdNP8@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: linkBe 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).