On 05.10.21 23:54, Segher Boessenkool wrote:
Hi!
On Tue, Oct 05, 2021 at 10:16:47PM +0200, Thomas Koenig wrote:
On 04.10.21 16:14, Jakub Jelinek via Fortran wrote:
Based on some IRC discussion, yet another option would be bump libgfortran
SONAME (on all arches), make real(kind=16) on powerpc64
Have been scrutinising the GCC 11.2 Download. I would appreciate if you start
including the gcc source files for the documentation
in the release as well.
Có Uh R rr r rv
Được gửi r cg vwtừ iPhone của tôi để ge rrb
On Wed, 6 Oct 2021 at 13:07, dimechc via Gcc wrote:
>
> Have been scrutinising the GCC 11.2 Download. I would appreciate if you start
> including the gcc source files for the documentation
> in the release as well.
They should be present already. Which documentation are you talking about?
I got the GCC 11.2 download, but cannot locate the doc directory used to
produce the
gcc documentation manuals.
‐‐‐ Original Message ‐‐‐
On Wednesday, October 6th, 2021 at 12:32 PM, Jonathan Wakely
wrote:
> On Wed, 6 Oct 2021 at 13:07, dimechc via Gcc gcc@gcc.gnu.org wrote:
>
> > Ha
On Wed, Oct 06, 2021 at 01:19:28PM +, dimechc via Gcc wrote:
> I got the GCC 11.2 download, but cannot locate the doc directory used to
> produce the
> gcc documentation manuals.
gcc/doc/, gcc/*/*.texi, libstdc++-v3/doc/, lib*/*.texi, ...
Jakub
On Wed, 6 Oct 2021, 14:19 dimechc, wrote:
> I got the GCC 11.2 download, but cannot locate the doc directory used to
> produce the
> gcc documentation manuals.
>
You still haven't said which documentation you're talking about.
GCC has lots of documentation. All the sources should be in the rel
On Wed, Oct 06, 2021 at 08:59:53AM +0200, Thomas Koenig wrote:
> On 05.10.21 23:54, Segher Boessenkool wrote:
> >>There is also the issue of binary data. If some user has written
> >>out data in double double and wants to read it in as IEEE quad,
> >>the results are going to be garbage. Another o
On Wed, Oct 06, 2021 at 10:17:44AM -0500, Segher Boessenkool wrote:
> On Wed, Oct 06, 2021 at 08:59:53AM +0200, Thomas Koenig wrote:
> > On 05.10.21 23:54, Segher Boessenkool wrote:
> > >>There is also the issue of binary data. If some user has written
> > >>out data in double double and wants to
On Wed, Oct 6, 2021 at 11:19 AM Segher Boessenkool
wrote:
>
> On Wed, Oct 06, 2021 at 08:59:53AM +0200, Thomas Koenig wrote:
> > On 05.10.21 23:54, Segher Boessenkool wrote:
> > >>There is also the issue of binary data. If some user has written
> > >>out data in double double and wants to read it
‐‐‐ Original Message ‐‐‐
On Wednesday, October 6th, 2021 at 2:50 PM, Jonathan Wakely
wrote:
> On Wed, 6 Oct 2021, 14:19 dimechc, wrote:
>
>> I got the GCC 11.2 download, but cannot locate the doc directory used to
>> produce the
>> gcc documentation manuals.
>
> You still haven't said
On Wed, Oct 06, 2021 at 03:57:35PM +, dimechc via Gcc wrote:
> ‐‐‐ Original Message ‐‐‐
> On Wednesday, October 6th, 2021 at 2:50 PM, Jonathan Wakely
> wrote:
>
> > On Wed, 6 Oct 2021, 14:19 dimechc, wrote:
> >
> >> I got the GCC 11.2 download, but cannot locate the doc directory us
Hi all,
FYI The next RISC-V GNU Toolchain Biweekly Sync is cancelled because
the developers from mainland China are still on their National Holiday.
There were not too much new topics in the past weeks, except a few
psABI issues, which could be postponed to the next meeting.
--
Best wishes,
Wei
On Wed, Oct 06, 2021 at 05:41:07PM +0200, Jakub Jelinek wrote:
> On Wed, Oct 06, 2021 at 10:17:44AM -0500, Segher Boessenkool wrote:
> > On Wed, Oct 06, 2021 at 08:59:53AM +0200, Thomas Koenig wrote:
> > > >That means flipping the default on all PowerPC to no longer be double-
> > > >double. This
On Wed, 6 Oct 2021 at 16:57, dimechc wrote:
>
>
>
>
> ‐‐‐ Original Message ‐‐‐
> On Wednesday, October 6th, 2021 at 2:50 PM, Jonathan Wakely
> wrote:
>
>
>
> On Wed, 6 Oct 2021, 14:19 dimechc, wrote:
>>
>> I got the GCC 11.2 download, but cannot locate the doc directory used to
>> prod
On Wed, Oct 06, 2021 at 11:42:17AM -0400, David Edelsohn wrote:
> On Wed, Oct 6, 2021 at 11:19 AM Segher Boessenkool
> wrote:
> >
> > On Wed, Oct 06, 2021 at 08:59:53AM +0200, Thomas Koenig wrote:
> > > On 05.10.21 23:54, Segher Boessenkool wrote:
> > > >>There is also the issue of binary data. I
-‐‐ Original Message ‐‐‐
On Wednesday, October 6th, 2021 at 4:10 PM, Jonathan Wakely
wrote:
> On Wed, 6 Oct 2021 at 16:57, dimechc dime...@protonmail.com wrote:
>
> > ‐‐‐ Original Message ‐‐‐
> >
> > On Wednesday, October 6th, 2021 at 2:50 PM, Jonathan Wakely
> > jwakely@gm
On Wed, Oct 06, 2021 at 11:07:30AM -0500, Segher Boessenkool wrote:
> We can emulate it everywhere (using libquadmath for example). This can
> magically make -msoft-float work as well everywhere, btw.
Emulation is one thing, but another one is where are those __float128 or
quad long double argume
On Wed, Oct 06, 2021 at 06:34:33PM +0200, Jakub Jelinek wrote:
> On Wed, Oct 06, 2021 at 11:07:30AM -0500, Segher Boessenkool wrote:
> > We can emulate it everywhere (using libquadmath for example). This can
> > magically make -msoft-float work as well everywhere, btw.
>
> Emulation is one thing,
On Wed, Oct 06, 2021 at 11:59:37AM -0500, Segher Boessenkool wrote:
> On Wed, Oct 06, 2021 at 06:34:33PM +0200, Jakub Jelinek wrote:
> > On Wed, Oct 06, 2021 at 11:07:30AM -0500, Segher Boessenkool wrote:
> > > We can emulate it everywhere (using libquadmath for example). This can
> > > magically
On Wed, 6 Oct 2021, Jakub Jelinek via Gcc wrote:
> On Wed, Oct 06, 2021 at 11:07:30AM -0500, Segher Boessenkool wrote:
> > We can emulate it everywhere (using libquadmath for example). This can
> > magically make -msoft-float work as well everywhere, btw.
>
> Emulation is one thing, but another
On Wed, Oct 6, 2021 at 12:21 PM Segher Boessenkool
wrote:
>
> On Wed, Oct 06, 2021 at 11:42:17AM -0400, David Edelsohn wrote:
> > On Wed, Oct 6, 2021 at 11:19 AM Segher Boessenkool
> > wrote:
> > >
> > > On Wed, Oct 06, 2021 at 08:59:53AM +0200, Thomas Koenig wrote:
> > > > On 05.10.21 23:54, Seg
On Wed, Oct 06, 2021 at 07:07:43PM +0200, Jakub Jelinek wrote:
> On Wed, Oct 06, 2021 at 11:59:37AM -0500, Segher Boessenkool wrote:
> > On Wed, Oct 06, 2021 at 06:34:33PM +0200, Jakub Jelinek wrote:
> > > On Wed, Oct 06, 2021 at 11:07:30AM -0500, Segher Boessenkool wrote:
> > > > We can emulate it
On Wed, Oct 06, 2021 at 05:13:59PM +, Joseph Myers wrote:
> On Wed, 6 Oct 2021, Jakub Jelinek via Gcc wrote:
> > On Wed, Oct 06, 2021 at 11:07:30AM -0500, Segher Boessenkool wrote:
> > > We can emulate it everywhere (using libquadmath for example). This can
> > > magically make -msoft-float wo
On 10/6/21 12:50 PM, Segher Boessenkool wrote:
> So we have three options (well, four):
>
> 0) Do nothing. We will stay in this hell forever. Not my choice :-)
> 1) Use a soft-float-like parameter passing everywhere. This works but
>will be horridly slow on newer systems. We can do better
On Wed, 6 Oct 2021, Segher Boessenkool wrote:
> Soft float is not described in any formal ABI btw (well, except the
> Power 32-bit embedded ABI :-) ) -- it is an compiler-internal affair.
It's fully documented in the unified 32-bit ABI document (under
ATR-SOFT-FLOAT conditionals).
There's still
On Wed, Oct 06, 2021 at 07:42:31PM +, Joseph Myers wrote:
> On Wed, 6 Oct 2021, Segher Boessenkool wrote:
> > Soft float is not described in any formal ABI btw (well, except the
> > Power 32-bit embedded ABI :-) ) -- it is an compiler-internal affair.
>
> It's fully documented in the unified 3
On Wed, 6 Oct 2021, Segher Boessenkool wrote:
> > There's still some code in the compiler for a very old soft-float ABI for
> > binary128 long double (passing by reference, using _q_* libcall names). I
> > don't really think it makes much sense to use that for future _Float128
> > support for
On Wed, 6 Oct 2021, Segher Boessenkool wrote:
> With "not in any" I mean: not for other architectures either! All archs
> that do not say anything about floating point in their machine
> description get a working sofware floating point (for binary32 and
> binary64 currently).
Any architecture th
On Mon, Oct 04, 2021 at 12:07:54PM +0200, Jakub Jelinek wrote:
> etc. Could we just pretend in the compiler to libgfortran ABI that
> powerpc64le-linux real(kind=16) is kind 17 and make sure that if anything
> would actually think it is 17 bytes it uses 16 instead (though, kind=10
> on x86-64 or i
On Wed, Oct 06, 2021 at 10:17:44AM -0500, Segher Boessenkool wrote:
> On Wed, Oct 06, 2021 at 08:59:53AM +0200, Thomas Koenig wrote:
> > On 05.10.21 23:54, Segher Boessenkool wrote:
> > >>There is also the issue of binary data. If some user has written
> > >>out data in double double and wants to
On 07.10.21 05:35, Michael Meissner via Fortran wrote:
I tried this at one point. There are a lot of hidden assumptions that the kind
number is the number of bytes. I'm sure it can be tracked down, but the
problem is with these assumptions is you can't prove a negative (i.e. you never
know that
32 matches
Mail list logo
