public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Michael Meissner <meissner@linux.ibm.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Michael Meissner <meissner@linux.ibm.com>,
	Jonathan Wakely <jwakely@redhat.com>,
	libstdc++ <libstdc++@gcc.gnu.org>,
	gcc-patches <gcc-patches@gcc.gnu.org>,
	Bill Schmidt <wschmidt@linux.ibm.com>,
	David Edelsohn <dje.gcc@gmail.com>,
	Segher Boessenkool <segher@kernel.crashing.org>,
	Peter Berner <bergner@linux.ibm.com>
Subject: Re: [PATCH] libstdc++: Add C++ runtime support for new 128-bit long double format
Date: Tue, 1 Dec 2020 18:32:54 -0500	[thread overview]
Message-ID: <20201201233254.GA11298@ibm-toto.the-meissners.org> (raw)
In-Reply-To: <CAH6eHdRHkZTMuZtK=mOrL6Oh7M7gjA+MeT769EyEwm9AeMwr7Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3117 bytes --]

Note this is just to keep the gcc-patches archive up to date.  I originally
posted this reply but the attached config.log file was too big.  It was also
sent directly to Jonathan, and he replied.  So I canceled the gcc-patches post,
and I'm sending out this one with a bzip2's config.log:

On Tue, Dec 01, 2020 at 09:10:30PM +0000, Jonathan Wakely wrote:
> On Tue, 1 Dec 2020 at 19:13, Michael Meissner via Libstdc++
> <libstdc++@gcc.gnu.org> wrote:
> >
> > On Tue, Dec 01, 2020 at 04:04:30PM +0000, Jonathan Wakely wrote:
> > > On 01/12/20 15:10 +0000, Jonathan Wakely wrote:
> > > >On 30/11/20 16:30 -0500, Michael Meissner via Libstdc++ wrote:
> > > >>Jonathan, could you send a fresh set of patches (or at least replacements)?  I
> > > >>tried installing the patches on a master branch I checked out this morning, and
> > > >>I got two rejects:
> > > >
> > > >I don't understand why those chunks failed, but I'll rebase and send a
> > > >new patch ASAP.
> > >
> > > Here's the rebased patch, with regenerated autoconf files and a fix
> > > for the <ext/numeric_limits.h> header. I'd changed it since sending
> > > the previous patch, and broke the "there's more than one long double"
> > > case (i.e. the _GLIBCXX_LONG_DOUBLE_ALT128_COMPAT case).
> >
> > Unfortunately this patch DOES NOT work at all.
> >
> > If I build a compiler with the configure option:
> >         --with-long-double-format=ieee
> >
> > And I compile this simple program:
> >
> >         #include <iostream>
> >
> >         int main(int argc, char *argv[], char *envp[])
> >         {
> >           std::cout << "Hello World!\n";
> >           return 0;
> >         }
> >
> > I get all of these errors:
> 
> It works fine for me (see below). I think your symptoms are due to
> using a glibc that doesn't support the new long double, and so
> libstdc++ support for it is also disabled. You need at least glibc
> 2.32 for the libstdc++ changes to be enabled.

I am using the Advance Toolchain which includes GLIBC 2.32, which has the
necessary support.  I will include the config.log as an attachment.

Note, I am also using the patches I submitted around November 19th.

In particular, there is the patch that maps long double built-in names if long
double is IEEE 128-bit:
https://gcc.gnu.org/pipermail/gcc-patches/2020-November/559659.html

I used the patch that tries to fix some problems with gnu attributes:
https://gcc.gnu.org/pipermail/gcc-patches/2020-November/559657.html

I used the patch that fixes up the gnu attributes use in libgcc:
https://gcc.gnu.org/pipermail/gcc-patches/2020-November/559660.html

I used the patch that adds float128 <-> Decimal conversions:
https://gcc.gnu.org/pipermail/gcc-patches/2020-November/559661.html

I used the patch that allows -mabi={ieee,ibm}longdouble to override the default
configuration for long double == 64 bits, without having to use the
-mlong-double-64 option as well:
https://gcc.gnu.org/pipermail/gcc-patches/2020-November/559660.html

-- 
Michael Meissner, IBM
IBM, M/S 2506R, 550 King Street, Littleton, MA 01460-6245, USA
email: meissner@linux.ibm.com, phone: +1 (978) 899-4797

[-- Attachment #2: libstdc++-v3-config.log.bz2 --]
[-- Type: application/x-bzip2, Size: 24642 bytes --]

  parent reply	other threads:[~2020-12-01 23:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-11 21:50 Jonathan Wakely
2020-11-30 21:30 ` Michael Meissner
2020-12-01 15:10   ` Jonathan Wakely
2020-12-01 16:04     ` Jonathan Wakely
2020-12-01 19:10       ` Michael Meissner
2020-12-01 21:10         ` Jonathan Wakely
2020-12-01 21:41           ` Jonathan Wakely
     [not found]           ` <20201201222501.GA18971@ibm-toto.the-meissners.org>
2020-12-01 22:36             ` Jonathan Wakely
2020-12-01 23:24               ` Michael Meissner
2020-12-02 15:14               ` Michael Meissner
2020-12-01 23:32           ` Michael Meissner [this message]
2020-12-03 23:07       ` Tulio Magno Quites Machado Filho
2020-12-04  0:35         ` Jonathan Wakely
2020-12-10 16:14           ` Jonathan Wakely
2020-12-10 17:14             ` Peter Bergner
2020-12-10 17:27               ` Jonathan Wakely
2020-12-15  0:57             ` Tulio Magno Quites Machado Filho
2020-11-30 23:29 ` Segher Boessenkool
2020-12-01 15:04   ` Jonathan Wakely

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=20201201233254.GA11298@ibm-toto.the-meissners.org \
    --to=meissner@linux.ibm.com \
    --cc=bergner@linux.ibm.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.com \
    --cc=jwakely@redhat.com \
    --cc=libstdc++@gcc.gnu.org \
    --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).