public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/105371] The result of the merge function is different when it's type of parameters is the extensions type of derived type
Date: Mon, 10 Oct 2022 19:28:33 +0000 [thread overview]
Message-ID: <bug-105371-4-zyLPbdn2WD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105371-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105371
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2022-10-10
Status|UNCONFIRMED |NEW
Keywords| |wrong-code
CC| |anlauf at gcc dot gnu.org
--- Comment #8 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #4)
> Thing is, I have to find a compiler that gives the result the reporter
> expects.
Update: the NAG compiler 7.1 seems to be the only compiler that behaves
as expected by the user.
The somewhat modified testcase shows that not only simplification of MERGE,
but also the generated code behaves inconsistently:
program p
implicit none
type t
integer :: c
end type
type, extends (t) :: t2
integer :: c2
end type
class(t), allocatable :: x, y, r
integer :: i = 1
x = t2(1,-1)
y = t2(2,-2)
r = x
call check_type()
r = merge (x, x, i == 1)
call check_type ()
r = merge (y, y, i == 2)
call check_type ()
r = merge (x, y, i == 2)
call check_type ()
contains
subroutine check_type ()
select type (z => r)
type is (t)
print *, "type is (t) :", z% c
type is (t2)
print *, "type is (t2):", z% c, z% c2
end select
end subroutine
end program p
NAG 7.1 prints:
type is (t2): 1 -1
type is (t2): 1 -1
type is (t2): 2 -2
type is (t2): 2 -2
Current gfortran:
type is (t2): 1 -1
type is (t) : 1
type is (t) : 2
type is (t2): 2 -2
As MERGE is expanded inline, I was hoping to understand what happens here,
but a first look at the dump-tree looked strange for the second and third
case. Needs further investigation.
prev parent reply other threads:[~2022-10-10 19:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 0:56 [Bug fortran/105371] New: " xudong.luo@compiler-dev.com
2022-04-25 7:03 ` [Bug fortran/105371] " schwab@linux-m68k.org
2022-04-26 18:12 ` kargl at gcc dot gnu.org
2022-04-27 9:28 ` xudong.luo@compiler-dev.com
2022-04-27 19:51 ` anlauf at gcc dot gnu.org
2022-04-27 22:14 ` sgk at troutmask dot apl.washington.edu
2022-04-28 0:10 ` xudong.luo@compiler-dev.com
2022-04-28 7:00 ` xudong.luo@compiler-dev.com
2022-10-10 19:28 ` anlauf at gcc dot gnu.org [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-105371-4-zyLPbdn2WD@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).