public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tydeman.fred at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug math/26108] exp10() has problems with <tgmath.h>
Date: Wed, 10 Jun 2020 23:01:03 +0000	[thread overview]
Message-ID: <bug-26108-131-Vrmi4Xq4ko@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26108-131@http.sourceware.org/bugzilla/>

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

--- Comment #1 from Fred Tydeman <tydeman.fred at gmail dot com> ---
That problem shows up on Intel x86 64-bit Fedora Linux 32 with gcc 10.

Using clang 10, I also get mismatches between specific and generic for fadd,
fsub, fmul, fdiv.

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

  reply	other threads:[~2020-06-10 23:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-10 22:40 [Bug math/26108] New: " tydeman.fred at gmail dot com
2020-06-10 23:01 ` tydeman.fred at gmail dot com [this message]
2020-06-10 23:03 ` [Bug math/26108] " joseph at codesourcery dot com
2020-06-10 23:06 ` joseph at codesourcery dot com
2021-09-30 20:41 ` cvs-commit at gcc dot gnu.org
2021-09-30 20:42 ` jsm28 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-26108-131-Vrmi4Xq4ko@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).