From: Tobias Burnus <tobias@codesourcery.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>, fortran <fortran@gcc.gnu.org>
Subject: Re: [r12-2511 Regression] FAIL: gfortran.dg/PR93963.f90 -Os execution test on Linux/x86_64
Date: Tue, 27 Jul 2021 10:41:46 +0200 [thread overview]
Message-ID: <38be0476-7bfc-3506-3186-473129f0a215@codesourcery.com> (raw)
In-Reply-To: <20210726172732.0269C2864701@gskx-2.sc.intel.com>
The automatic regression test of Sunil wrote:
On 26.07.21 19:27, sunil.k.pandey wrote:
> commit 0cbf03689e3e7d9d6002b8e5d159ef3716d0404c
> PR fortran/93308/93963/94327/94331/97046 problems raised by descriptor handling
> caused
> FAIL: gfortran.dg/PR93963.f90 -O2 execution test
> ...
(That's on x86-64-gnu-linux but (only) with -m32.)
I have filled: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101635
Let's see how soon we can fix this – otherwise, we have to XFAIL this testcase.
I don't completely understand why this only occurred with -m32,
but I believe it is an alias issue. The whole handling of the conversion
(prep code, library call, post-library handling) looks extremely fragile
and this is not the first issue in that this code causes.
I think the proper solution – having tons of advantages - is to move the
library code to the compiler itself and making use of the compile-time
known type, rank, etc. knowledge.
Tobias
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
prev parent reply other threads:[~2021-07-27 8:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 17:27 sunil.k.pandey
2021-07-27 8:41 ` Tobias Burnus [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=38be0476-7bfc-3506-3186-473129f0a215@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@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).