From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id E7C0B3858C83; Wed, 11 Jan 2023 14:03:48 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E7C0B3858C83
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1673445828;
	bh=n04UrC0wrd4J6CJ/nLSRwgJyxpwcMpfAUGKngZ09j3M=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=lajCVDNE/+iQsHBksXxdK1O6WqUxxMJRnPUaBcRCeXaMQuxfwSrQDZyCY+P9oF1+p
	 5io5p2K/6JTMQe7q82bGoaJNL7P06RSsv5ufe2s3BpJgQRQfPFJdsCda2QaRAVDROH
	 vo+9kUw3zqCyw1FdrZBUluL+EhzhbPdu5zxRpnec=
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/108349] LTO mismatch for __builtin_realloc between
 glibc and gfortran frontend
Date: Wed, 11 Jan 2023 14:03:48 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-108349-4-px1ES3T8HU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-108349-4@http.gcc.gnu.org/bugzilla/>
References: <bug-108349-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

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

Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |burnus at gcc dot gnu.org,
                   |                            |tschwinge at gcc dot gnu.o=
rg,
                   |                            |vries at gcc dot gnu.org

--- Comment #6 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
As nvptx target is known to be sensitive to such mismatches (outside of the=
 LTO
context reported here), I individually did test this commit
r13-5100-g0986c351aa8a9f08b3cb614baec13564dd62c114 "fortran: Fix up function
types for realloc and sincos{,f,l} builtins [PR108349]", and found that it =
also
resolves the following nvptx target compilation failures:

'gfortran.dg/pr35662.f90':

    ptxas /tmp/ccYNgEEN.o, line 44; error   : Illegal operand type to
instruction 'st'
    ptxas /tmp/ccYNgEEN.o, line 51; error   : Type of argument does not mat=
ch
formal parameter '%in_ar0'
    ptxas /tmp/ccYNgEEN.o, line 51; error   : Alignment of argument does not
match formal parameter '%in_ar0'
    ptxas /tmp/ccYNgEEN.o, line 44; error   : Unknown symbol '%stack'
    ptxas fatal   : Ptx assembly aborted due to errors
    nvptx-as: ptxas returned 255 exit status

'gfortran.fortran-torture/compile/pr37236.f':

    ptxas [...]/build-gcc/gcc/testsuite/gfortran/pr37236.o, line 269; error=
   :
Illegal operand type to instruction 'st'
    ptxas [...]/build-gcc/gcc/testsuite/gfortran/pr37236.o, line 275; error=
   :
Type of argument does not match formal parameter '%in_ar0'
    ptxas [...]/build-gcc/gcc/testsuite/gfortran/pr37236.o, line 269; error=
   :
Unknown symbol '%stack'
    ptxas fatal   : Ptx assembly aborted due to errors
    nvptx-as: ptxas returned 255 exit status

These are now all-PASS.


In the nvptx target gfortran test suite logs remain however dozens more sim=
ilar
instances.  I've not checked if what's underlying those would also be expos=
ing
the same kind of LTO problem.=