public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-94694-4-nnWvPMou5I@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94694-4@http.gcc.gnu.org/bugzilla/>

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

--- 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 fortran
> > build is enabled on aarch64-elf and thus we can resolve this by adding
> > aarch64-elf-*) to
> > 
> > # Disable Fortran for some systems.
> > case "${target}" in
> >   mmix-*-*)
> >     # See <http://gcc.gnu.org/ml/gcc-patches/2004-11/msg00572.html>.
> >     unsupported_languages="$unsupported_languages fortran"
> >     ;;
> >   bpf-*-*)
> >     unsupported_languages="$unsupported_languages fortran"
> >     ;;
> > esac
> > 
> > technically aarch64-elf isn't a primary architecture.
> 
> 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.
> 
> 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=c,c++ is relevant for bootstrap.

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

  parent reply	other threads:[~2020-04-21 15:55 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21 14:35 [Bug libfortran/94694] New: [libgfortran] " akrl at gcc dot gnu.org
2020-04-21 14:39 ` [Bug libfortran/94694] " akrl at gcc dot gnu.org
2020-04-21 14:40 ` [Bug libfortran/94694] [10 Regression][libgfortran] " ktkachov at gcc dot gnu.org
2020-04-21 15:05 ` rguenth at gcc dot gnu.org
2020-04-21 15:07 ` rguenth at gcc dot gnu.org
2020-04-21 15:32 ` jakub at gcc dot gnu.org
2020-04-21 15:40 ` rearnsha at gcc dot gnu.org
2020-04-21 15:55 ` rguenth at gcc dot gnu.org [this message]
2020-04-21 16:04 ` jakub at gcc dot gnu.org
2020-04-21 16:25 ` foreese at gcc dot gnu.org
2020-04-21 16:31 ` jakub at gcc dot gnu.org
2020-04-21 16:40   ` Andrea Corallo
2020-04-21 16:40 ` andrea.corallo at arm dot com
2020-04-21 16:45 ` jakub at gcc dot gnu.org
2020-04-21 17:04 ` foreese at gcc dot gnu.org
2020-04-21 17:13 ` jakub at gcc dot gnu.org
2020-04-21 17:14 ` jakub at gcc dot gnu.org
2020-04-21 17:23 ` jakub at gcc dot gnu.org
2020-04-21 17:37 ` rguenther at suse dot de
2020-04-21 17:42 ` jakub at gcc dot gnu.org
2020-04-21 18:10 ` foreese at gcc dot gnu.org
2020-04-21 19:06 ` jakub at gcc dot gnu.org
2020-04-21 19:40 ` jakub at gcc dot gnu.org
2020-04-21 21:03 ` foreese at gcc dot gnu.org
2020-04-21 22:43 ` jakub at gcc dot gnu.org
2020-04-22 11:21 ` andrea.corallo at arm dot com
2020-04-22 14:12 ` jakub at gcc dot gnu.org
2020-04-22 14:17 ` foreese at gcc dot gnu.org
2020-04-22 14:29 ` foreese at gcc dot gnu.org
2020-04-22 14:52 ` jakub at gcc dot gnu.org
2020-04-22 19:34 ` cvs-commit at gcc dot gnu.org
2020-04-23 14:12 ` cvs-commit at gcc dot gnu.org
2020-04-23 14:38 ` jakub at gcc dot gnu.org
2020-04-23 15:17 ` andrea.corallo at arm dot com

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-94694-4-nnWvPMou5I@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).