public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug math/30550] powerpc64le: GCC-specific code for isinf() is being used on clang Date: Fri, 30 Jun 2023 22:13:27 +0000 [thread overview] Message-ID: <bug-30550-131-hHzqmBtKZm@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30550-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30550 --- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tulio Magno Quites Machado Filho <tuliom@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=0a9e93842d8e535ac8174cb4ff7fb830b20e4ae7 commit 0a9e93842d8e535ac8174cb4ff7fb830b20e4ae7 Author: Tulio Magno Quites Machado Filho <tuliom@redhat.com> Date: Tue Jun 13 18:56:33 2023 -0300 Stop applying a GCC-specific workaround on clang [BZ #30550] GCC was the only compiler affected by the issue with __builtin_isinf_sign and float128. Fix BZ #30550. Reported-by: Qiu Chaofan <qiucofan@cn.ibm.com> Reviewed-by: Florian Weimer <fweimer@redhat.com> -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-06-30 22:13 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-13 21:46 [Bug math/30550] New: " tuliom at ascii dot art.br 2023-06-13 21:47 ` [Bug math/30550] " tuliom at ascii dot art.br 2023-06-13 21:58 ` tuliom at ascii dot art.br 2023-06-30 22:13 ` cvs-commit at gcc dot gnu.org [this message] 2023-06-30 22:18 ` tuliom at ascii dot art.br
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-30550-131-hHzqmBtKZm@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: linkBe 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).