public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gustavowalbon at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/97543] powerpc64le: libgcc has unexpected long double in .gnu_attribute
Date: Fri, 23 Oct 2020 18:14:10 +0000	[thread overview]
Message-ID: <bug-97543-4-ILJ2tzrpIe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97543-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97543

Gustavo Walbon <gustavowalbon at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gustavowalbon at gmail dot com

--- Comment #1 from Gustavo Walbon <gustavowalbon at gmail dot com> ---
I have seeing a bunch of packages failing because this warning of linker when I
build several packages on Alpine for PowerPc.

I have a alpine container running on a PowerPC 8, and I rebuilt the all gcc
packages with the flags --with-long-double-64 and --without-long-double-128 to
avoid this error, but that still happens 

I used the same code as Tulio to reproduce that warning.

~ $ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/powerpc64le-alpine-linux-musl/10.2.0/lto-wrapper
Target: powerpc64le-alpine-linux-musl
Configured with: /home/devel/aports/main/gcc/src/gcc-10.2.0/configure
--prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info
--build=powerpc64le-alpine-linux-musl --host=powerpc64le-alpine-linux-musl
--target=powerpc64le-alpine-linux-musl --with-pkgversion='Alpine 10.2.0'
--enable-checking=release --disable-fixed-point --disable-libstdcxx-pch
--disable-multilib --disable-nls --disable-werror --disable-symvers
--enable-__cxa_atexit --enable-default-pie --enable-default-ssp
--enable-cloog-backend --enable-languages=c,c++,objc,go,fortran,ada
--with-abi=elfv2 --enable-secureplt --enable-decimal-float=no
--enable-targets=powerpcle-linux --with-long-double-64
--without-long-double-128 --disable-libquadmath --disable-libssp
--disable-libmpx --disable-libmudflap --disable-libsanitizer --enable-shared
--enable-threads --enable-tls --with-system-zlib --with-linker-hash-style=gnu
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 10.2.0 (Alpine 10.2.0)

~ $ gcc -O0 -mlong-double-64 test-ldouble64.c && ./a.out
/usr/lib/gcc/powerpc64le-alpine-linux-musl/10.2.0/../../../../powerpc64le-alpine-linux-musl/bin/ld:
/tmp/ccHidlkA.o uses 64-bit long double,
/usr/lib/gcc/powerpc64le-alpine-linux-musl/10.2.0/../../../../lib/libgcc_s.so.1
uses 128-bit long double
/usr/lib/gcc/powerpc64le-alpine-linux-musl/10.2.0/../../../../powerpc64le-alpine-linux-musl/bin/ld:
/tmp/ccHidlkA.o uses 64-bit long double,
/usr/lib/gcc/powerpc64le-alpine-linux-musl/10.2.0/../../../../lib/libgcc_s.so.1
uses 128-bit long double
sizeof(long double) = 8
a * b = 16.000000

  reply	other threads:[~2020-10-23 18:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-23 13:32 [Bug libgcc/97543] New: " tuliom at ascii dot art.br
2020-10-23 18:14 ` gustavowalbon at gmail dot com [this message]
2020-10-23 18:36 ` [Bug libgcc/97543] " bergner at gcc dot gnu.org
2020-10-23 19:14 ` segher at gcc dot gnu.org
2020-10-23 23:28 ` bergner at gcc dot gnu.org
2020-10-24  2:48 ` meissner at gcc dot gnu.org
2020-10-24  3:33 ` amodra at gmail dot com
2020-10-24  7:06 ` meissner at gcc dot gnu.org
2020-10-24  7:32 ` meissner at gcc dot gnu.org
2020-10-26 19:21 ` segher at gcc dot gnu.org
2020-12-03 19:52 ` cvs-commit at gcc dot gnu.org
2020-12-29 13:39 ` gustavowalbon at gmail dot com
2021-01-21  1:41 ` 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-97543-4-ILJ2tzrpIe@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: 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).