public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "newbie-02 at gmx dot de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug math/28472] pow(10, i) accuracy
Date: Sun, 14 Nov 2021 05:38:00 +0000	[thread overview]
Message-ID: <bug-28472-131-S10OOBmb6P@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28472-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=28472

--- Comment #5 from b. <newbie-02 at gmx dot de> ---
if ... I'm right in testing ... Intel 'oneAPI' compiler(s) 'icpx' and 'dpcpp'
produce clean powers of 10 ( matching E-string evaluation ) for long double
figures with 'exp10l( x )'.  

since they do not compile themselves but use clang/clang++ for this purpose -
with a huge bunch of options and includes - it should be possible to have a
look at it and gather some inspiration ... ??? hot spots seem to be calling
clang with '-cc1' and '-x c++'.  

( for the bug itself i propose testing and setting to new, besides the
deviation it is a consistency problem which is difficult to explain to users:
that one get's different results in one system for different formulations of
the same  mathematical task. ('pow( 10, x )' != '1Ex' != 'pow10( x )' !=
'exp10( x )' ).  

( and of course gcc shouldn't be second in 'best compilers' ) 

reg. the proposal of using exp10( x ) instead of pow( 10, x ):  
'exp10( x )' compiled with gcc -O2: 230 fails between x = -324 and x = 308, 
'pow( 10, x )': only 2, 
as well with 'exp10( x )' 
( complaining " incompatible implicit declaration of built-in function ‘exp10’
" ) 
as for '__builtin_exp10( x )'.  
as well for gcc, g++, clang++, 
'clang' additional complaints and producing even more fails.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-11-14  5:38 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-18 23:54 [Bug math/28472] New: " mwelinder at gmail dot com
2021-10-19 15:44 ` [Bug math/28472] " joseph at codesourcery dot com
2021-10-19 21:28 ` mwelinder at gmail dot com
2021-10-19 21:42 ` joseph at codesourcery dot com
2021-10-25  8:44 ` newbie-02 at gmx dot de
2021-11-14  5:38 ` newbie-02 at gmx dot de [this message]
2022-01-24 21:45 ` mwelinder at gmail dot com
2022-01-24 21:56 ` joseph at codesourcery dot com
2022-09-23 16:33 ` newbie-02 at gmx dot de
2023-01-09 14:43 ` newbie-02 at gmx dot de
2023-01-09 18:35 ` joseph at codesourcery dot com
2023-01-09 21:23 ` newbie-02 at gmx dot de
2023-01-09 21:36 ` joseph at codesourcery dot com
2023-01-10  0:23 ` newbie-02 at gmx dot de
2024-03-02 22:53 ` vincent-srcware at vinc17 dot net
2024-03-04 14:58 ` wdijkstr at arm dot com
2024-03-04 15:35 ` vincent-srcware at vinc17 dot net
2024-03-04 16:07 ` wdijkstr at arm dot com
2024-03-04 17:09 ` vincent-srcware at vinc17 dot net
2024-03-04 18:27 ` wdijkstr at arm dot com
2024-03-04 19:23 ` vincent-srcware at vinc17 dot net
2024-03-18 21:09 ` newbie-02 at gmx dot de
2024-03-18 22:17 ` wdijkstr at arm dot com
2024-03-20  9:02 ` newbie-02 at gmx dot de
2024-03-20  9:56 ` vincent-srcware at vinc17 dot net
2024-03-20 13:54 ` wdijkstr at arm dot com

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-28472-131-S10OOBmb6P@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).