Hi Jakub,
clearly there is still work to fix (but seems e.g. most of the lto tests
are related to the gnu attributes stuff:( ).
This is looking better than what I expected. Apart from LTO, I expect
that a couple of files still do not have the correct flags set when
compiling, or maybe some t
On Mon, Jan 03, 2022 at 06:03:41PM +0100, Thomas Koenig wrote:
> On 03.01.22 17:26, Jakub Jelinek wrote:
>
> > so we could similarly have something like:
> > #if !(defined(__powerpc64__) && __BYTE_ORDER__ == __ORDER_LITTLE_ENDIAN__
> > && __SIZEOF_LONG_DOUBLE__ == 16)
> > _gfortran_transfer_
Dear all,
the initial-data-target for a pointer initialization can be either
NULL() or a non-constant target. In the latter case subscripts of
the target specification (or substring starting and ending points)
must be constant expressions. The patch adds corresponding checks.
I have verified th
On 03.01.22 17:26, Jakub Jelinek wrote:
so we could similarly have something like:
#if !(defined(__powerpc64__) && __BYTE_ORDER__ == __ORDER_LITTLE_ENDIAN__ &&
__SIZEOF_LONG_DOUBLE__ == 16)
_gfortran_transfer_complex128;
_gfortran_transfer_complex128_write;
#endif
...
#if !(defined(
Hi Jakub,
So, either we'd need to add e.g. preprocessing support for gfortran.map
or some other way how to make certain symbols appear conditionally at
different symbol versions, or another option would be to choose different
symbol names for those for the powerpc64le-linux cases
(e.g._gfortra
On Mon, Jan 03, 2022 at 04:36:21PM +0100, Jakub Jelinek via Gcc-patches wrote:
> The following patch adds the library side of -mabi=ieeelongdouble
> I/O support.
>
> There is one issue to be resolved though, for the sake of libgfortran.a
> built on an older powerpc64le-linux system (glibc older th
On 03.01.22 16:24, Jakub Jelinek via Fortran wrote:
Ok for power-ieee128?
OK.
Thanks!
Best regards
Thomas
Hi!
Here is the compiler side of those changes, but depends of course
on the decision what to do with those *real128* and *complex128* symbols.
With all the 4 patches e.g. print *, var for real(kind=16) var; var = 1.0;
works both with -mabi=ibmlongdouble and -mabi=ieeelongdouble.
2022-01-03 Jak
Hi!
The following patch adds the library side of -mabi=ieeelongdouble
I/O support.
There is one issue to be resolved though, for the sake of libgfortran.a
built on an older powerpc64le-linux system (glibc older than 2.32) and
then deployed on glibc 2.32 or later, I believe we want to use
_gfortra
Hi Jakub,
On Mon, Jan 03, 2022 at 11:33:32AM +0100, Jakub Jelinek wrote:
The idea behind this is that libstdc++ is written such that it can handle
both IBM extended and IEEE quad long double, so its object files are
compatible with both.
Now tested on powerpc64le-linux (and together with the
Hi!
Testing found that we also need libquadmath to be built with
-mno-gnu-attribute, otherwise -mabi=ieeelongdouble programs don't link.
Ok for power-ieee128?
2022-01-03 Jakub Jelinek
* configure.ac: Set XCFLAGS to -mno-gnu-attribute on
powerpc64le*-linux*.
* configur
Hello world,
the attached patch lets the library compile correctly, as far as I
have been able to determine.
Committed to the branch.
Best regards
Thomas
Make sure the Fortran specifics have real(kind=16).
This brings the library to compile with all specific functions.
It also correc
On Mon, Jan 03, 2022 at 11:33:32AM +0100, Jakub Jelinek wrote:
> The idea behind this is that libstdc++ is written such that it can handle
> both IBM extended and IEEE quad long double, so its object files are
> compatible with both.
Now tested on powerpc64le-linux (and together with the regenerat
Hi!
On Mon, Jan 03, 2022 at 11:19:21AM +0100, Thomas Koenig wrote:
> One additional point. The linker does not understand
> -mno-gnu-attribute:
That is a GCC option, not an ld one. If you use it to compile some
file there will be no .gnu.attributes section generated for that
translation unit.
On Mon, Jan 03, 2022 at 11:19:21AM +0100, Thomas Koenig wrote:
> > > 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 switc
On 02.01.22 23:58, Thomas Koenig wrote:
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
16 matches
Mail list logo
