public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/55601] libgfortran build fails with --disable-libquadmath
Date: Mon, 10 Dec 2012 08:41:00 -0000	[thread overview]
Message-ID: <bug-55601-4-XrrYiz82no@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55601-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55601

--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-12-10 08:41:36 UTC ---
Hmm, seemingly, the check ignores --disable-libquadmath-support by only testing
for C's __float support, cf. libgfortran/acinclude.m4's LIBGFOR_CHECK_FLOAT128.

gfortran itself is checked via libgfortran/acinclude.m4's
LIBGFOR_WORKING_GFORTRAN.

One probably should augment the C test by a Fortran "REAL(16)" test.
Additionally, one could directly honour --disable-libquadmath-support, which I
think is also passed to libgfortran's configure.


Regarding the --disable-libquadmath combined with --enable-libquadmath-support:
Some warning would be useful, but the question is how to trigger it.


  parent reply	other threads:[~2012-12-10  8:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-05  3:32 [Bug libfortran/55601] New: " danglin at gcc dot gnu.org
2012-12-05  8:52 ` [Bug libfortran/55601] " burnus at gcc dot gnu.org
2012-12-09  0:37 ` pinskia at gcc dot gnu.org
2012-12-10  8:41 ` burnus at gcc dot gnu.org [this message]
2014-04-30  4:33 ` brooks at gcc dot gnu.org

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-55601-4-XrrYiz82no@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).