From: Thomas Koenig <tkoenig@netcologne.de>
To: Michael Meissner <meissner@linux.ibm.com>,
Bill Schmidt <wschmidt@linux.ibm.com>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
Jakub Jelinek <jakub@redhat.com>,
Segher Boessenkool <segher@kernel.crashing.org>,
Peter Bergner <bergner@linux.ibm.com>,
David Edelsohn <dje.gcc@gmail.com>,
gcc mailing list <gcc@gcc.gnu.org>
Subject: [power-iee128] How to specify linker flags
Date: Sun, 2 Jan 2022 23:58:29 +0100 [thread overview]
Message-ID: <541fa494-ce3c-50f2-367b-f0dd492dcf45@netcologne.de> (raw)
In-Reply-To: <YYA2FMfDR0yehJLA@toto.the-meissners.org>
Hi Michael,
> If you are building libraries that contain modules with multiple long double
> types, you must use the '-mno-gnu-attribute'. We also use the '-Wno-psabi'
> option, which silences the warning that you are switching long double types (if
> glibc is not 2.34 or newer). We may need to tweak -Wno-psabi for use with
> Fortran.
I am now at the point where the object files are also compiled correctly
for the gfortran specifics:
0000000000000000 <_gfortran_specific__abs_r17>:
0: 09 00 43 f4 lxv vs34,0(r3)
4: 48 16 40 fc xsabsqp v2,v2
8: 20 00 80 4e blr
However, the linker complains, as you said it would, about the different
formats:
/opt/at15.0/bin/ld: .libs/maxloc0_4_r16.o uses IBM long double,
.libs/_abs_r17.o uses IEEE long double
/opt/at15.0/bin/ld: failed to merge target specific data of file
.libs/_abs_r17.o
I know next to nothing about libtool, so I do not know how to
add the flags so the linker can find them.
Any pointers?
(I have not yet committed the changes because I do not want to
commit something that does not compile. If anybody wants to
take a look, it's on the ieee128 virtual machine under
/home/tkoenig/ieee ).
Regards
Thomas
next prev parent reply other threads:[~2022-01-02 22:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 14:43 [RFC] User-visible changes for powerpc64-le-linux ABI changes Thomas Koenig
2021-11-01 15:54 ` Bill Schmidt
2021-11-01 17:32 ` Thomas Koenig
2021-11-01 17:45 ` Jakub Jelinek
2021-11-02 6:19 ` Thomas Koenig
2021-11-04 4:41 ` Michael Meissner
2021-11-01 18:46 ` Michael Meissner
2021-11-15 20:27 ` Thomas Koenig
2021-11-15 22:14 ` Peter Bergner
2021-11-15 23:42 ` Michael Meissner
2021-11-16 7:51 ` Thomas Koenig
2021-11-19 14:19 ` Jakub Jelinek
2021-11-19 17:30 ` Segher Boessenkool
2021-11-19 19:09 ` Thomas Koenig
2021-11-19 19:36 ` Peter Bergner
2021-11-19 21:30 ` Segher Boessenkool
2022-01-02 22:58 ` Thomas Koenig [this message]
2022-01-03 10:19 ` [power-iee128] How to specify linker flags Thomas Koenig
2022-01-03 10:33 ` Jakub Jelinek
2022-01-03 15:23 ` [power-iee128] libgfortran: Use -mno-gnu-attribute in libgfortran Jakub Jelinek
2022-01-03 15:27 ` Thomas Koenig
2022-01-03 10:34 ` [power-iee128] How to specify linker flags Segher Boessenkool
2022-01-05 21:20 ` Michael Meissner
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=541fa494-ce3c-50f2-367b-f0dd492dcf45@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=meissner@linux.ibm.com \
--cc=segher@kernel.crashing.org \
--cc=wschmidt@linux.ibm.com \
/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).