public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "alexandre.poux at coria dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/112700] Segmentation fault with list of characters and types
Date: Mon, 27 Nov 2023 08:59:23 +0000	[thread overview]
Message-ID: <bug-112700-4-K2iRKwEO1B@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112700-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Alexandre Poux <alexandre.poux at coria dot fr> ---
Among the things that avoid the ICE:
- Using a subroutine instead of a function
- not using a type procedure but a regular function
- wrapping the list of char in a custom type
- returning a list of a real numbers

Among the things that do not avoid the ICE:
- replacing the fixed length array with a pointer or an allocatable

      parent reply	other threads:[~2023-11-27  8:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-24 13:59 [Bug fortran/112700] New: " alexandre.poux at coria dot fr
2023-11-24 19:31 ` [Bug fortran/112700] " anlauf at gcc dot gnu.org
2023-11-27  8:59 ` alexandre.poux at coria dot fr [this message]

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-112700-4-K2iRKwEO1B@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).