[pushed] wwwdocs: readings: Remove Herman D. Knoble's Fortran Resources

2023-02-01 Thread Gerald Pfeifer
The original page is gone, and search engines did not reveal a new location. If any of you has a new location, feel free to add that (or let me know and I'll take care). Gerald --- htdocs/readings.html | 5 - 1 file changed, 5 deletions(-) diff --git a/htdocs/readings.html b/htdocs/readings

libquadmath, glibc, and the Q format flag

2023-02-01 Thread Florian Weimer via Fortran
I recently discovered that libquadmath registers custom printf callbacks on load. As far as I can tell, this is done so that the Q format flag can be used to print floating point numbers, using format strings such as "%Qf". To enable Q flag processing, libquadmath has to register replacements for

Re: libquadmath, glibc, and the Q format flag

2023-02-01 Thread Jakub Jelinek via Fortran
On Wed, Feb 01, 2023 at 11:56:42AM +0100, Florian Weimer via Gcc wrote: > I recently discovered that libquadmath registers custom printf callbacks > on load. As far as I can tell, this is done so that the Q format flag > can be used to print floating point numbers, using format strings such > as "

Re: libquadmath, glibc, and the Q format flag

2023-02-01 Thread Florian Weimer via Fortran
* Jakub Jelinek: > On Wed, Feb 01, 2023 at 11:56:42AM +0100, Florian Weimer via Gcc wrote: >> I recently discovered that libquadmath registers custom printf callbacks >> on load. As far as I can tell, this is done so that the Q format flag >> can be used to print floating point numbers, using for

Re: libquadmath, glibc, and the Q format flag

2023-02-01 Thread Jakub Jelinek via Fortran
On Wed, Feb 01, 2023 at 12:29:02PM +0100, Florian Weimer via Gcc wrote: > >> This impacts most (all?) Fortran code on GNU/Linux because libgfortran > >> depends on libquadmath. > > > > Not anymore. > > If GCC is configured against new enough glibc (with _Float128 support) > > libgfortran.so.5 is no

[og12] Fix 'omp_allocator_handle_kind' example in 'gfortran.dg/gomp/allocate-4.f90' (was: [PATCH 1/5] [gfortran] Add parsing support for allocate directive (OpenMP 5.0).)

2023-02-01 Thread Thomas Schwinge
Hi! On 2022-01-13T14:53:16+, Hafiz Abid Qadeer wrote: > Currently we only make use of this directive when it is associated > with an allocate statement. These changes (or a variant thereof; haven't checked) are present on devel/omp/gcc-12 branch as commit 491478d12b83e102f72858e8a871a25c951d

Re: [og12] Fix 'omp_allocator_handle_kind' example in 'gfortran.dg/gomp/allocate-4.f90' (was: [PATCH 1/5] [gfortran] Add parsing support for allocate directive (OpenMP 5.0).)

2023-02-01 Thread Tobias Burnus
Hi Thomas, On 01.02.23 12:59, Thomas Schwinge wrote: + ! Don't do this (..., but it does pass the checks). + !$omp allocate (var1) allocator(10_omp_allocator_handle_kind) ! { dg-bogus "Expected integer expression of the 'omp_allocator_handle_kind' kind" } + allocate (var1(x)) + + ! Assumtio

Re: [pushed] wwwdocs: readings: Remove Herman D. Knoble's Fortran Resources

2023-02-01 Thread David Malcolm via Fortran
On Wed, 2023-02-01 at 10:56 +0100, Gerald Pfeifer wrote: > The original page is gone, and search engines did not reveal a new > location. > > If any of you has a new location, feel free to add that (or let me > know and I'll take care). FWIW the most recent version in archive.org is here: https:

[PATCH, committed] Fortran: error recovery on invalid array section [PR108609]

2023-02-01 Thread Harald Anlauf via Fortran
Dear all, the fix for PR108527 came with a testcase that revealed a latent bug with array sections and invalid array declarations. The ICE first popped up on powerpc64-linux-gnu (big endian), but the issue was not so clear as such on x86_64-pc-linux-gnu, as it did not show up e.g. in valgrind. T