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] New: [gfortran] MERGE does not copy ALLOCATABLE property of derived type Date: Thu, 06 Aug 2020 13:17:04 +0000 [thread overview] Message-ID: <bug-96495-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96495 Bug ID: 96495 Summary: [gfortran] MERGE does not copy ALLOCATABLE property of derived type Product: gcc Version: 10.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: paul.luckner@rwth-aachen.de Target Milestone: --- Created attachment 49011 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49011&action=edit proof of concept code There is a bug in gfortran and I singled out the problem this far: - a derived type with ALLOCATABLE data - a MERGE call - an operator overloading used as argument to the MERGE call - ELEMENTAL procedure it is best to look at the proof of concept codes attached. There are 4 highlighted code sections which should all yield similar results but only one works whereas the others are broken. The bug arises when called using a vector (using the ELEMENTAL feature). ==================== Supplementary information $ gfortran --version GNU Fortran (GCC) 10.1.0 $ gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/opt/exports/gcc-10.1.0/bin/../libexec/gcc/x86_64-pc-linux-gnu/10.1.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: ../gcc-10.1.0-source/gcc-10.1.0/configure --enable-languages=c,c++,fortran --enable-checking=release --disable-libstdcxx-pch --enable-libgomp --enable-lto --enable-gold --with-plugin-ld=gold --prefix=/usr/local/gcc-10.1.0 Thread model: posix Supported LTO compression algorithms: zlib gcc version 10.1.0 (GCC) $ cat /etc/os-release NAME="openSUSE Leap" VERSION="15.1"
next reply other threads:[~2020-08-06 13:17 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-06 13:17 paul.luckner@rwth-aachen.de [this message] 2020-08-11 13:35 ` [Bug fortran/96495] " paul.luckner@rwth-aachen.de 2020-08-11 13:53 ` 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@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).