public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: Newlib <newlib@sourceware.org>
Subject: fenv support vs. SMP systems
Date: Mon, 13 Jul 2020 08:19:03 +0200	[thread overview]
Message-ID: <d1d42490-7464-2613-09f8-d163583bdb49@embedded-brains.de> (raw)

Hello,

the new fenv support alters usually some floating-point status and 
control register. This register is usually specific to the processor 
executing the code. In an SMP system, the current approach can lead to 
an inconsistent system if the register is not included in the thread 
context (for example in RTEMS these registers are considered to be 
system wide and are only initialized during the system startup). What do 
I mean with inconsistent system? For example, you set the rounding mode 
on processor A to from X (= default) to Y, then the you migrate to 
processor B and suddenly use the default rounding mode X. Another 
example is to do a division by zero on processor A and then migrate to 
processor B and check the exception flags.

-- 
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  : sebastian.huber@embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.

             reply	other threads:[~2020-07-13  6:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-13  6:19 Sebastian Huber [this message]
2020-07-13 13:00 ` Joel Sherrill
2020-07-13 17:16   ` Joseph Myers
2020-07-13 21:03     ` Joel Sherrill
2020-07-14  5:16     ` Sebastian Huber

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=d1d42490-7464-2613-09f8-d163583bdb49@embedded-brains.de \
    --to=sebastian.huber@embedded-brains.de \
    --cc=newlib@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).