Hi Michael.
I have sort of (I used the i370 target of GCC 3.2.3 instead
of the s390 target) reproduced Jesus's work with z/PDOS
which can be obtained from here:
http://www.pdos.org/zpdos.zip
You can see that with standard Hercules 3.13:
18:02:24 Hercules Version 3.13
18:02:24 (c)Copyright 1999
Hi,
On Fri, Oct 01 2021, Gerald Pfeifer wrote:
> On Wed, 29 Sep 2021, Maxim Kuvyrkov via Gcc wrote:
>> Configurations that track master branches have 3-day intervals.
>> Configurations that track release branches — 6 days. If a regression is
>> detected it is narrowed down to component first —
> On 8 Oct 2021, at 07:35, Thomas Koenig via Fortran
> wrote:
>
>
> On 07.10.21 17:33, Jakub Jelinek wrote:
>>> It will also be a compatibility issue if users have code compiled on a LE
>>> system with GCC 11 and earlier with KIND=16, it will not link with GCC 12.
>> libgfortran ABI changed
Hi Iain,
If one wanted to prioritize library SO name stability - then, perhaps, the
approach Jonathan mentioned has been used for libstdc++ (add new
symbols for ieee128 with a different mangling to the existing r/c_16 ..)
would be preferable (the FE then has to choose the relevant symbol/
mangli
On Wed, Oct 06, 2021 at 10:03:59PM +, Joseph Myers wrote:
> 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 floatin
On Wed, Oct 06, 2021 at 11:42:11PM -0400, Michael Meissner 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:
> > > On 05.10.21 23:54, Segher Boessenkool wrote:
> > > >>There is also the issue of binary dat
Snapshot gcc-10-20211008 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/10-20211008/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 10 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Hi Iain,
Things get interesting for user code, calling a routine compiled
for double double with newer IEEE QP will result in breakage.
That would not happen with the proposal above, since the library would
have different entry points for the two formats.
I meant the case where the user wri
Hi Thomas,
recognising that this is complex - the intent here is to see if there are ways
to partition the problem (where the pain falls does depend on the choices
made).
perhaps:
*A library (interface, name)
*B compiler internals
*C user-facing changes
> On 8 Oct 2021, at 17:26, Thomas K
> On 8 Oct 2021, at 23:55, Thomas Koenig via Gcc wrote:
>
>
> Hi Iain,
>
>>> Things get interesting for user code, calling a routine compiled
>>> for double double with newer IEEE QP will result in breakage.
>> That would not happen with the proposal above, since the library would
>> have di
On Fri, 1 Oct 2021, Nelson Ribeiro via Gcc wrote:
> Hello.
>
> Firstly I want to apologize for this long post, but in a way this post also
> is meant for documenting the work that I have done hunting down this issue.
> Secondly I must say that I do not have much insights on the GCC internals,
> onl
11 matches
Mail list logo
