public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "meissner at gcc dot gnu.org" <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: Sat, 24 Oct 2020 07:06:43 +0000	[thread overview]
Message-ID: <bug-97543-4-6iddX6AdGC@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

--- Comment #7 from Michael Meissner <meissner at gcc dot gnu.org> ---
Just to be clear, my patch only turns on -mno-gnu-attributes on compiling
ibm-ldouble.c.  That is the module that has the extended IBM 128-bit support in
it.

However, I believe if any module in libgcc_s.so has the IBM extended long
double attributes set, it essentially taints the entire shared library.

At least on 64-bit little endian Linux, it does not use long double at all.  It
uses __ibm128 explicitly.

However, t-linux and t-ibm-ldouble both explicitly set -mlong-double-128. 
Since long double is explicitly set to 128-bit, it sets the gnu attributes for
__ibm128 (since internally __ibm128 is mapped to long double in this case).

  parent reply	other threads:[~2020-10-24  7:06 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 ` [Bug libgcc/97543] " gustavowalbon at gmail dot com
2020-10-23 18:36 ` 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 [this message]
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-6iddX6AdGC@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).