public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: <libc-alpha@sourceware.org>
Subject: [04/12] Add fesetexcept: arm
Date: Thu, 11 Aug 2016 21:00:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.20.1608112059300.1591@digraph.polyomino.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.20.1608112053120.1591@digraph.polyomino.org.uk>

This patch adds an ARM version of fesetexcept.

2016-08-11  Joseph Myers  <joseph@codesourcery.com>

	* sysdeps/arm/fesetexcept.c: New file.

diff --git a/sysdeps/arm/fesetexcept.c b/sysdeps/arm/fesetexcept.c
new file mode 100644
index 0000000..96a79ae
--- /dev/null
+++ b/sysdeps/arm/fesetexcept.c
@@ -0,0 +1,38 @@
+/* Set given exception flags.  ARM version.
+   Copyright (C) 2016 Free Software Foundation, Inc.
+   This file is part of the GNU C Library.
+
+   The GNU C Library is free software; you can redistribute it and/or
+   modify it under the terms of the GNU Lesser General Public
+   License as published by the Free Software Foundation; either
+   version 2.1 of the License, or (at your option) any later version.
+
+   The GNU C Library is distributed in the hope that it will be useful,
+   but WITHOUT ANY WARRANTY; without even the implied warranty of
+   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+   Lesser General Public License for more details.
+
+   You should have received a copy of the GNU Lesser General Public
+   License along with the GNU C Library; if not, see
+   <http://www.gnu.org/licenses/>.  */
+
+#include <fenv.h>
+#include <fpu_control.h>
+#include <arm-features.h>
+
+int
+fesetexcept (int excepts)
+{
+  fpu_control_t fpscr, new_fpscr;
+
+  /* Fail if a VFP unit isn't present unless nothing needs to be done.  */
+  if (!ARM_HAVE_VFP)
+    return (excepts != 0);
+
+  _FPU_GETCW (fpscr);
+  new_fpscr = fpscr | (excepts & FE_ALL_EXCEPT);
+  if (new_fpscr != fpscr)
+    _FPU_SETCW (new_fpscr);
+
+  return 0;
+}

-- 
Joseph S. Myers
joseph@codesourcery.com

  parent reply	other threads:[~2016-08-11 21:00 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11 20:57 [01/12] Add fesetexcept Joseph Myers
2016-08-11 20:59 ` [03/12] Add fesetexcept: alpha Joseph Myers
2016-08-11 20:59 ` [02/12] Add fesetexcept: aarch64 Joseph Myers
2016-08-11 21:45   ` Paul Eggert
2016-08-11 23:30     ` Joseph Myers
2016-08-11 21:00 ` [05/12] Add fesetexcept: hppa Joseph Myers
2016-08-11 21:00 ` Joseph Myers [this message]
2016-08-11 21:01 ` [06/12] Add fesetexcept: ia64 Joseph Myers
2016-08-11 21:01 ` [07/12] Add fesetexcept: m68k Joseph Myers
2016-08-11 21:02 ` [08/12] Add fesetexcept: mips Joseph Myers
2016-08-11 21:02 ` [09/12] Add fesetexcept: powerpc Joseph Myers
2016-08-12 16:18   ` Paul E. Murphy
2016-08-12 16:30     ` Joseph Myers
2016-08-12 16:47       ` Paul E. Murphy
2016-08-12 17:50         ` Joseph Myers
2016-08-11 21:03 ` [10/12] Add fesetexcept: s390 Joseph Myers
2016-08-15  8:07   ` Stefan Liebler
2016-08-15 20:52     ` Joseph Myers
2016-08-11 21:04 ` [11/12] Add fesetexcept: sh Joseph Myers
2016-08-11 21:04 ` [12/12] Add fesetexcept: sparc Joseph Myers
2016-08-12  7:32   ` Jose E. Marchesi
2016-08-12 11:15     ` Joseph Myers
2016-08-13  8:32       ` Jose E. Marchesi
2016-08-12 15:49 ` [01/12] Add fesetexcept Paul E. Murphy
2016-08-12 16:20   ` Joseph Myers
2016-08-12 17:25     ` Paul E. Murphy
2016-08-12 17:39       ` Joseph Myers

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=alpine.DEB.2.20.1608112059300.1591@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.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).