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 EC6BB3870852; Tue, 21 Apr 2020 15:55:21 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EC6BB3870852
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1587484521;
 bh=hukLBmKwwuqOkgL7T/wG8IsqSVtnrYolX6s7cEFjcLE=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=JUMJqD+ibH4unbZuYTEN7HF2WMPbKbcgssbhPMzYPDQsREeXN/XM7P/rzYujPQ2IM
 8OTIfVHR6vr6LOwC/xYP7ciCG1W8Ke+0BpD5oQnyfO7NKLmYgZtao2MsW5GG4FUiPy
 RC4iqMalvtnsj9DffOP6taH27O96FbLhi6K7lyKQ=
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/94694] [10 Regression][libgfortran] libgfortran does
 not compile on bare-metal aarch64-none-elf (newlib)
Date: Tue, 21 Apr 2020 15:55:21 +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: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-94694-4-nnWvPMou5I@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-94694-4@http.gcc.gnu.org/bugzilla/>
References: <bug-94694-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
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <http://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <http://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2020 15:55:22 -0000

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

--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Richard Earnshaw from comment #5)
> (In reply to Richard Biener from comment #2)
...
> > Since Fortran isn't release critical the only P1-ish part is that fortr=
an
> > build is enabled on aarch64-elf and thus we can resolve this by adding
> > aarch64-elf-*) to
> >=20
> > # Disable Fortran for some systems.
> > case "${target}" in
> >   mmix-*-*)
> >     # See <http://gcc.gnu.org/ml/gcc-patches/2004-11/msg00572.html>.
> >     unsupported_languages=3D"$unsupported_languages fortran"
> >     ;;
> >   bpf-*-*)
> >     unsupported_languages=3D"$unsupported_languages fortran"
> >     ;;
> > esac
> >=20
> > technically aarch64-elf isn't a primary architecture.
>=20
> Well in that case it should *test* the run time for compatibility.  It
> shouldn't assume it's incompatible just because of the target triplet.
>=20
> aarch64-elf is a secondary platform.  It should still build.

Sure, that makes it P1-ish.  But since fortran and thus its runtime
library are not part of the release criteria disabling it [by default]
is a valid fix for that.  Or one could read the criteria that
only --enable-languages=3Dc,c++ is relevant for bootstrap.

Yeah, the criteria as written are probably not the best, but they are
what they are.=