From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 27F7E385DC0D; Tue, 14 Apr 2020 12:55:46 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 27F7E385DC0D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1586868946; bh=ZHDBqxjN/DFLeZCeOQQXG31J3CGRui1ZCFPTy5yZiLc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=AlMP3/ptk/0prfgeRif+Fq1uUAs5AKWHs66LiM0rpSkUKtimXgtJTVTznPxpZlwWr 240lcy6xjGT8B8MS+5BsUFI3rq/uLn97j6uB4Z0A1P/+hs7gwBzqcFfuTfFepSj3ml Gt/0dWKmlQ/aPaDNRVtyD+abmbHPJjDvijZu8Bko= From: "dave.anglin at bell dot net" To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/94586] trigd_lib.inc:84:28: error: implicit declaration of function 'fmaf' Date: Tue, 14 Apr 2020 12:55:45 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libfortran X-Bugzilla-Version: 10.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dave.anglin at bell dot net X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Apr 2020 12:55:46 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94586 --- Comment #4 from dave.anglin at bell dot net --- On 2020-04-13 11:02 p.m., kargl at gcc dot gnu.org wrote: > Does math.h define fmaf? If yes, this this is bogus bug report. > If no, please disable building gfortran on hppa64. No, math.h does not define fmaf. Build was okay as of 20200403: https://gcc.gnu.org/pipermail/gcc-testresults/2020-April/558420.html =3D=3D=3D gfortran tests =3D=3D=3D Running target unix FAIL: gfortran.dg/unlimited_polymorphic_30.f03 -O0 execution test FAIL: gfortran.dg/unlimited_polymorphic_30.f03 -O1 execution test FAIL: gfortran.dg/unlimited_polymorphic_30.f03 -O2 execution test FAIL: gfortran.dg/unlimited_polymorphic_30.f03 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test FAIL: gfortran.dg/unlimited_polymorphic_30.f03 -O3 -g execution test FAIL: gfortran.dg/unlimited_polymorphic_30.f03 -Os execution test =3D=3D=3D gfortran Summary =3D=3D=3D # of expected passes 51686 # of unexpected failures 6 # of expected failures 201 # of unsupported tests 428 /test/gnu/gcc/objdir/gcc/testsuite/gfortran/../../gfortran version 10.0.1 20200403 (experimental) (GCC)=20 I presume this was introduced by the following commit: commit 57391ddaf39f7cb85825c32e83feb1435889da51 Author: Fritz Reese Date:=C2=A0=C2=A0 Tue Apr 7 11:59:36 2020 -0400 =C2=A0=C2=A0=C2=A0 Fix PR fortran/93871 and re-implement degree-valued trig= onometric intrinsics. =C2=A0=C2=A0=C2=A0 2020-04-01=C2=A0 Fritz Reese=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 Steven G. Kargl=C2=A0 =C2=A0=C2=A0=C2=A0 gcc/fortran/ChangeLog =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 PR fortr= an/93871=