public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "here.is.a.gcc.bug at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/99549] New: Segfault when scalar argument of elemental function is both derived type with allocatable component and a function result
Date: Thu, 11 Mar 2021 11:47:03 +0000	[thread overview]
Message-ID: <bug-99549-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 99549
           Summary: Segfault when scalar argument of elemental function is
                    both derived type with allocatable component and a
                    function result
           Product: gcc
           Version: 10.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: here.is.a.gcc.bug at gmail dot com
  Target Milestone: ---

Created attachment 50363
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50363&action=edit
A self-contained fortran program which causes the bug.

An elemental function is called where one argument is an array and another
argument is a scalar.

If the scalar argument is both:
  - A derived type with an allocatable component
  - The result of a function call (an rvalue in c++ speak)

Then a segfault happens.

             reply	other threads:[~2021-03-11 11:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11 11:47 here.is.a.gcc.bug at gmail dot com [this message]
2021-03-11 12:18 ` [Bug fortran/99549] " rguenth at gcc dot gnu.org
2021-03-12 11:53 ` marxin 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-99549-4@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).