From: Bill Schmidt <wschmidt@linux.ibm.com>
To: Thomas Koenig <tkoenig@netcologne.de>, Jakub Jelinek <jakub@redhat.com>
Cc: gcc mailing list <gcc@gcc.gnu.org>,
David Edelsohn <dje.gcc@gmail.com>,
Segher Boessenkool <segher@kernel.crashing.org>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
Michael Meissner <meissner@linux.ibm.com>,
Peter Bergner <bergner@linux.ibm.com>
Subject: Re: [power-ieee128] What should the math functions be annotated with?
Date: Fri, 3 Dec 2021 08:57:54 -0600 [thread overview]
Message-ID: <c805280c-c0af-ff2c-9d44-709a70b3ea6f@linux.ibm.com> (raw)
In-Reply-To: <f279f5c7-82a4-6070-b775-03e06d3aed6b@netcologne.de>
Hi!
On 12/3/21 5:56 AM, Thomas Koenig wrote:
>
> Hi Jakub,
>
>> Note, we want to test both building gcc on ppc64le with older glibc
>> and newer glibc (and that libgfortran will have the same ABI between both
>> and one can move gcc including libgfortran and libquadmath from the older
>> glibc setup to newer and make -mabi=ieeelongdouble work in Fortran too).
>
> Using an older glibc is no problem - we can use gcc135 on the compile
> farm for that.
>
> As far as the other options you outlined, I think I'll defer to people
> who know more about setting up libraries than I do. I have root access,
> but chances are I would just mess up the virtual machine :-)
Easiest is probably to install the advance toolchain. Mike said he'll work on
that later this morning.
Thanks!
Bill
>
> Regards
>
> Thomas
next prev parent reply other threads:[~2021-12-03 14:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 20:34 Thomas Koenig
2021-12-01 20:54 ` Jakub Jelinek
2021-12-01 23:05 ` Jakub Jelinek
2021-12-03 7:29 ` Thomas Koenig
2021-12-03 9:28 ` Jakub Jelinek
2021-12-03 11:16 ` Thomas Koenig
2021-12-03 11:35 ` Jakub Jelinek
2021-12-03 11:56 ` Thomas Koenig
2021-12-03 14:57 ` Bill Schmidt [this message]
2021-12-04 6:39 ` Michael Meissner
2021-12-04 9:33 ` Thomas Koenig
2021-12-04 10:16 ` Thomas Koenig
2021-12-04 10:29 ` Jakub Jelinek
2021-12-04 13:42 ` Thomas Koenig
2021-12-04 15:25 ` Michael Meissner
2021-12-04 15:37 ` Peter Bergner
2021-12-04 16:12 ` Peter Bergner
2021-12-04 16:19 ` Jakub Jelinek
2021-12-04 22:27 ` Peter Bergner
2021-12-04 17:40 ` Thomas Koenig
2021-12-05 0:35 ` Peter Bergner
2021-12-05 11:16 ` Thomas Koenig
2021-12-06 22:31 ` 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=c805280c-c0af-ff2c-9d44-709a70b3ea6f@linux.ibm.com \
--to=wschmidt@linux.ibm.com \
--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=tkoenig@netcologne.de \
/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).