public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jb at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/48982] libgfortran on sysv never uses fpsetmask
Date: Fri, 20 May 2011 14:02:00 -0000	[thread overview]
Message-ID: <bug-48982-4-E6stykFNfZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48982-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Janne Blomqvist <jb at gcc dot gnu.org> 2011-05-20 13:40:47 UTC ---
Actually, in the version control log for acinclude.m4 we have

commit b00fa2cfbfd81cbdc31d5a44e4ce8140cc153776
Author: fxcoudert <fxcoudert@138bc75d-0d04-0410-961f-82ee72b054a4>
Date:   Fri Feb 25 17:56:04 2011 +0000

        * acinclude.m4 (LIBGFOR_CHECK_FPSETMASK): Set shell variable
        tested in configure.host.
        * configure: Regenerate.


    git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@170500
138bc75d-0d04-0410-961f-82ee72b054a4

And indeed the test is now

dnl Checks for fpsetmask function.
AC_DEFUN([LIBGFOR_CHECK_FPSETMASK], [
  AC_CACHE_CHECK([whether fpsetmask is present], libgfor_cv_have_fpsetmask, [
    AC_LINK_IFELSE([AC_LANG_PROGRAM([[
#if HAVE_FLOATINGPOINT_H
# include <floatingpoint.h>
#endif /* HAVE_FLOATINGPOINT_H */
#if HAVE_IEEEFP_H
# include <ieeefp.h>
#endif /* HAVE_IEEEFP_H */]],[[fpsetmask(0);]])],
    eval "libgfor_cv_have_fpsetmask=yes", eval "libgfor_cv_have_fpsetmask=no")
  ])
  if test x"$libgfor_cv_have_fpsetmask" = xyes; then
    have_fpsetmask=yes
    AC_DEFINE(HAVE_FPSETMASK, 1, [Define if you have fpsetmask.])
  fi
])


Can you test whether this works on 4.6?


  parent reply	other threads:[~2011-05-20 14:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-12 16:16 [Bug libfortran/48982] New: " nicolai.stange at zmaw dot de
2011-05-13 15:42 ` [Bug libfortran/48982] " nicolai.stange at zmaw dot de
2011-05-20 13:52 ` jb at gcc dot gnu.org
2011-05-20 14:02 ` jb at gcc dot gnu.org [this message]
2011-05-20 14:17 ` jb at gcc dot gnu.org
2011-05-20 14:43 ` nicolai.stange at zmaw dot de
2011-05-20 14:45 ` nicolai.stange at zmaw dot de
2011-05-28 16:28 ` nicolai.stange at zmaw dot de
2011-05-29  9:03 ` jb 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-48982-4-E6stykFNfZ@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).