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/102595] ICE in var_element, at fortran/decl.c:298 since r10-5607-gde89b5748d68b76b
Date: Sun, 15 Jan 2023 20:07:16 +0000	[thread overview]
Message-ID: <bug-102595-4-kPeIyZBh1t@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102595-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
I started to do some variations on the z1.f90 case:

program p
   complex, parameter :: x(0) = 2
   !data x%im /3.0/
   print *, x
end

Running this prints a blank line;

Looking at the -fdump-tree-original shows:

      parm.1.span = 8;
      parm.1.dtype = {.elem_len=8, .rank=1, .type=4};
      parm.1.dim[0].lbound = 1;
      parm.1.dim[0].ubound = 0;
      parm.1.dim[0].stride = 1;
      parm.1.data = (void *) &x[0];
      parm.1.offset = -1;

Is it valid to have an ubound less than the lbound?

program p
   complex, parameter :: x(1) = 2
   !data x%im /3.0/
   print *, x
end

The z2 case prints what is expected.  It looks like we need to catch something
in the parameter declaration before the data statement so that it is not
garbage later.

.. to be continued ..

  parent reply	other threads:[~2023-01-15 20:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-04 18:41 [Bug fortran/102595] New: ICE in var_element, at fortran/decl.c:298 gscfq@t-online.de
2021-10-05 20:00 ` [Bug fortran/102595] " anlauf at gcc dot gnu.org
2021-10-11  8:17 ` [Bug fortran/102595] ICE in var_element, at fortran/decl.c:298 since r10-5607-gde89b5748d68b76b marxin at gcc dot gnu.org
2021-12-23 20:13 ` kargl at gcc dot gnu.org
2021-12-23 20:15 ` kargl at gcc dot gnu.org
2021-12-23 23:20 ` kargl at gcc dot gnu.org
2022-12-30  3:26 ` cvs-commit at gcc dot gnu.org
2023-01-14  3:31 ` jvdelisle at gcc dot gnu.org
2023-01-15 20:07 ` jvdelisle at gcc dot gnu.org [this message]
2023-01-15 20:17 ` sgk at troutmask dot apl.washington.edu
2023-01-18  4:16 ` jvdelisle at gcc dot gnu.org
2023-01-21 23:24 ` cvs-commit at gcc dot gnu.org
2023-01-29  4:25 ` 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-102595-4-kPeIyZBh1t@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).