public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/114567] New: rs6000: explicit _Float128 doesn't generate optimal code Date: Wed, 03 Apr 2024 02:05:55 +0000 [thread overview] Message-ID: <bug-114567-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114567 Bug ID: 114567 Summary: rs6000: explicit _Float128 doesn't generate optimal code Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: linkw at gcc dot gnu.org Target Milestone: --- This is an issue which I happened to spot when I have been working on patches for PR112993. === test case === #define TYPE _Float128 #ifdef LD #undef TYPE #define TYPE long double #endif int sbm (TYPE *a) { return __builtin_signbit (*a); } ================== /opt/gcc-nightly/trunk/bin/gcc -mcpu=power8 -mvsx -O2 -mabi=ieeelongdouble -Wno-psabi test.c -DLD -S -o ref.s /opt/gcc-nightly/trunk/bin/gcc -mcpu=power8 -mvsx -O2 -mabi=ibmlongdouble -Wno-psabi test.c -S -o float128.s diff -Nur ref.s float128.s --- ref.s 2024-03-18 05:41:00.302208975 -0400 +++ float128.s 2024-03-18 05:41:00.392205513 -0400 @@ -9,7 +9,10 @@ sbm: .LFB0: .cfi_startproc - ld 3,8(3) + rldicr 3,3,0,59 + lxvd2x 0,0,3 + xxpermdi 0,0,0,2 + mfvsrd 3,0 srdi 3,3,63 blr .long 0
next reply other threads:[~2024-04-03 2:05 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-03 2:05 linkw at gcc dot gnu.org [this message] 2024-04-03 2:06 ` [Bug target/114567] " linkw at gcc dot gnu.org 2024-04-10 8:42 ` linkw 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-114567-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).