public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "murphyp at linux dot vnet.ibm.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/104253] New: libgcc missing __floatdiif Date: Wed, 26 Jan 2022 22:22:29 +0000 [thread overview] Message-ID: <bug-104253-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104253 Bug ID: 104253 Summary: libgcc missing __floatdiif Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: murphyp at linux dot vnet.ibm.com CC: bergner at gcc dot gnu.org, meissner at gcc dot gnu.org Target Milestone: --- When compiling something which uses the __ibm128 type, an instrinsic function call is generated which is not satisfied at link time. E.g foo.c: #include <stdio.h> #include <stdlib.h> int main(int a, char **v) { long d = strtol(v[1],0,0); __ibm128 i = d; printf("%a %a\n",__builtin_unpack_ibm128(i,0),__builtin_unpack_ibm128(i,1)); return 0; } gcc -O2 foo.c -o foo: /usr/bin/ld: /tmp/ccuWW1m0.o: in function `main': foo.c:(.text.startup+0x2c): undefined reference to `__floatdiif' collect2: error: ld returned 1 exit status This happens on a ppc64le machine running fedora rawhide, gcc -v: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/ppc64le-redhat-linux/12/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none OFFLOAD_TARGET_DEFAULT=1 Target: ppc64le-redhat-linux Configured with: ../configure --enable-bootstrap --enable-languages=c,c++,fortran,objc,obj-c++,ada,go,lto --prefix=/usr --mandir=/usr/share/man --infodir=/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 --enable-plugin --enable-initfini-array --with-isl=/builddir/build/BUILD/gcc-12.0.1-20220118/obj-ppc64le-redhat-linux/isl-install --enable-offload-targets=nvptx-none --without-cuda-driver --enable-offload-defaulted --enable-gnu-indirect-function --enable-secureplt --with-long-double-128 --with-long-double-format=ieee --with-cpu-32=power8 --with-tune-32=power8 --with-cpu-64=power8 --with-tune-64=power8 --build=ppc64le-redhat-linux --with-build-config=bootstrap-lto --enable-link-serialization=1 Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 12.0.1 20220118 (Red Hat 12.0.1-0) (GCC)
next reply other threads:[~2022-01-26 22:22 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-26 22:22 murphyp at linux dot vnet.ibm.com [this message] 2022-01-26 23:31 ` [Bug libgcc/104253] " meissner at gcc dot gnu.org 2022-01-26 23:52 ` joseph at codesourcery dot com 2022-01-26 23:53 ` jakub at gcc dot gnu.org 2022-01-27 19:42 ` meissner at gcc dot gnu.org 2022-01-27 19:45 ` meissner at gcc dot gnu.org 2022-01-28 18:39 ` [Bug target/104253] " jakub at gcc dot gnu.org 2022-01-28 20:30 ` jakub at gcc dot gnu.org 2022-01-28 21:09 ` meissner at gcc dot gnu.org 2022-01-28 22:23 ` meissner at gcc dot gnu.org 2022-01-31 10:30 ` jakub at gcc dot gnu.org 2022-01-31 18:43 ` meissner at gcc dot gnu.org 2022-02-14 22:42 ` cvs-commit at gcc dot gnu.org 2022-02-17 21:59 ` bergner at gcc dot gnu.org 2022-03-05 16:23 ` cvs-commit at gcc dot gnu.org 2022-03-06 1:16 ` cvs-commit at gcc dot gnu.org 2022-03-06 1:24 ` meissner at gcc dot gnu.org 2022-03-13 18:06 ` ebotcazou at gcc dot gnu.org 2022-03-14 17:03 ` bergner at gcc dot gnu.org 2022-04-06 20:51 ` bergner at gcc dot gnu.org 2022-04-07 10:47 ` ebotcazou at gcc dot gnu.org 2022-04-07 22:25 ` cvs-commit at gcc dot gnu.org 2022-04-11 15:21 ` cvs-commit at gcc dot gnu.org 2022-04-11 17:18 ` cvs-commit at gcc dot gnu.org 2022-04-11 17:26 ` cvs-commit 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-104253-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).