This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] Fix static-binary lazy FPU context allocation
- From: "Ryan S. Arnold" <ryan dot arnold at gmail dot com>
- To: Rich Felker <dalias at aerifal dot cx>
- Cc: "Maciej W. Rozycki" <macro at codesourcery dot com>, libc-alpha <libc-alpha at sourceware dot org>
- Date: Thu, 5 Sep 2013 12:18:43 -0500
- Subject: Re: [PATCH] Fix static-binary lazy FPU context allocation
- Authentication-results: sourceware.org; auth=none
- References: <alpine dot DEB dot 1 dot 10 dot 1308221904520 dot 8514 at tp dot orcam dot me dot uk> <20130822211407 dot GJ20515 at brightrain dot aerifal dot cx> <alpine dot DEB dot 1 dot 10 dot 1308222302050 dot 8514 at tp dot orcam dot me dot uk> <20130822225301 dot GK20515 at brightrain dot aerifal dot cx>
On Thu, Aug 22, 2013 at 5:53 PM, Rich Felker <dalias@aerifal.cx> wrote:
> My view is that any value that gives anything other than correct
> IEEE/Annex-F conforming behavior is an incorrect control word. Anyway,
> would it be correct to state that this whole issue is only relevant
> when the application is using the (undocumented?) feature of
> overriding the initial control word by defining its own __fpu_control
> symbol?
Sort of tangential to the conversation; When I implemented the Decimal
Floating Point library I discovered that the IEEE specification
(IEEE752-2008) decided to name a set of DFP rounding modes that were
only a subset of the actually hardware rounding modes available on
Power Architecture hardware. In my library I did see value in
allowing a user to set those additional rounding modes as well as the
ones defined in the IEEE spec.
Ryan