public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paul.luckner@rwth-aachen.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/96495] [gfortran] MERGE does not copy ALLOCATABLE property of derived type Date: Tue, 11 Aug 2020 13:35:10 +0000 [thread overview] Message-ID: <bug-96495-4-ensFeRiRVh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96495-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96495 paul.luckner@rwth-aachen.de changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #49011|0 |1 is obsolete| | --- Comment #1 from paul.luckner@rwth-aachen.de --- Created attachment 49042 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49042&action=edit proof of concept code -- version 2 I investigated further and the bug arises under the following circumstances: - derived type with ALLOCATABLE property - a binary ELEMENTAL operator - an unary operator The following code will crash f(1:2) = f(1:2) .binary. (.unary. f(1)) and the error message is as follows: "Program received signal SIGSEGV: Segmentation fault - invalid memory reference."
next prev parent reply other threads:[~2020-08-11 13:35 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-06 13:17 [Bug fortran/96495] New: " paul.luckner@rwth-aachen.de 2020-08-11 13:35 ` paul.luckner@rwth-aachen.de [this message] 2020-08-11 13:53 ` [Bug fortran/96495] " paul.luckner@rwth-aachen.de 2020-08-28 9:19 ` [Bug fortran/96495] [gfortran] Composition of user-defined operators " pault at gcc dot gnu.org 2020-08-29 12:04 ` pault at gcc dot gnu.org 2020-09-24 10:52 ` cvs-commit at gcc dot gnu.org 2020-09-26 11:41 ` cvs-commit at gcc dot gnu.org 2020-12-28 12:11 ` pault 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-96495-4-ensFeRiRVh@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).