public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jens.seifert at de dot ibm.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/100809] New: PPC: __int128 divide/modulo does not use P10 instructions vdivsq/vdivuq Date: Fri, 28 May 2021 07:58:35 +0000 [thread overview] Message-ID: <bug-100809-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100809 Bug ID: 100809 Summary: PPC: __int128 divide/modulo does not use P10 instructions vdivsq/vdivuq Product: gcc Version: 10.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: jens.seifert at de dot ibm.com Target Milestone: --- unsigned __int128 div(unsigned __int128 a, unsigned __int128 b) { return a/b; } __int128 div(__int128 a, __int128 b) { return a/b; } gcc -mcpu=power10 -save-temps -O2 int128.C Output: _Z3divoo: .LFB0: .cfi_startproc .localentry _Z3divoo,1 mflr 0 std 0,16(1) stdu 1,-32(1) .cfi_def_cfa_offset 32 .cfi_offset 65, 16 bl __udivti3@notoc addi 1,1,32 .cfi_def_cfa_offset 0 ld 0,16(1) mtlr 0 .cfi_restore 65 blr .long 0 .byte 0,9,0,1,128,0,0,0 .cfi_endproc .LFE0: .size _Z3divoo,.-_Z3divoo .globl __divti3 .align 2 .p2align 4,,15 .globl _Z3divnn .type _Z3divnn, @function _Z3divnn: .LFB1: .cfi_startproc .localentry _Z3divnn,1 mflr 0 std 0,16(1) stdu 1,-32(1) .cfi_def_cfa_offset 32 .cfi_offset 65, 16 bl __divti3@notoc addi 1,1,32 .cfi_def_cfa_offset 0 ld 0,16(1) mtlr 0 .cfi_restore 65 blr .long 0 .byte 0,9,0,1,128,0,0,0 .cfi_endproc Expected is the use of vdivsq/vdivuq. GCC version: /opt/rh/devtoolset-10/root/usr/bin/gcc -v Using built-in specs. COLLECT_GCC=/opt/rh/devtoolset-10/root/usr/bin/gcc COLLECT_LTO_WRAPPER=/opt/rh/devtoolset-10/root/usr/libexec/gcc/ppc64le-redhat-linux/10/lto-wrapper Target: ppc64le-redhat-linux Configured with: ../configure --enable-bootstrap --enable-languages=c,c++,fortran,lto --prefix=/opt/rh/devtoolset-10/root/usr --mandir=/opt/rh/devtoolset-10/root/usr/share/man --infodir=/opt/rh/devtoolset-10/root/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-shared --enable-threads=posix --enable-checking=release --enable-targets=powerpcle-linux --disable-multilib --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-linker-build-id --with-gcc-major-version-only --with-linker-hash-style=gnu --with-default-libstdcxx-abi=gcc4-compatible --enable-plugin --enable-initfini-array --with-isl=/builddir/build/BUILD/gcc-10.2.1-20200804/obj-ppc64le-redhat-linux/isl-install --disable-libmpx --enable-gnu-indirect-function --enable-secureplt --with-long-double-128 --with-cpu-32=power8 --with-tune-32=power8 --with-cpu-64=power8 --with-tune-64=power8 --build=ppc64le-redhat-linux Thread model: posix Supported LTO compression algorithms: zlib gcc version 10.2.1 20200804 (Red Hat 10.2.1-2) (GCC)
next reply other threads:[~2021-05-28 7:58 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-28 7:58 jens.seifert at de dot ibm.com [this message] 2021-05-28 8:12 ` [Bug c++/100809] " jens.seifert at de dot ibm.com 2021-06-01 14:59 ` wschmidt at gcc dot gnu.org 2021-06-01 22:55 ` meissner at gcc dot gnu.org 2021-06-01 22:58 ` meissner at gcc dot gnu.org 2021-06-04 20:17 ` meissner at gcc dot gnu.org 2021-07-08 1:56 ` [Bug target/100809] " cvs-commit at gcc dot gnu.org 2021-07-14 17:25 ` cvs-commit at gcc dot gnu.org 2021-07-14 17:53 ` meissner 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-100809-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).