Re: [PATCH] Fortran: fix treatment of character, value, optional dummy arguments [PR107444]

../../gcc/omp-low.cc:14662 0xd318a3 lower_omp_1 ../../gcc/omp-low.cc:14452 0xd318a3 lower_omp ../../gcc/omp-low.cc:14662 0xd377fb execute_lower_omp ../../gcc/omp-low.cc:14701 0xd377fb execute ../../gcc/omp-low.cc:14755 Please submit a full bug report, with preprocess

Re: [PATCH] Fortran: fix treatment of character, value, optional dummy arguments [PR107444]

On Nov 13 2022, Harald Anlauf wrote: > Can you please confirm that it fixes your issues? Looks good. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."

Re: [patch, fortran, doc] Explicitly mention undefined overflow

become visible to the > programmer. > * File operations on symbolic links:: > * File format of unformatted sequential files:: > * Asynchronous I/O:: > +* Behavior on integer overflow::o s/o$// -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69

Re: [PATCH] Fortran: fix passing of optional dummy as actual to optional argument [PR55978]

On Jun 24 2024, Mikael Morin wrote: > tree-pretty-print.cc's op_symbol_code handles them as: > > case TRUTH_AND_EXPR: > case TRUTH_ANDIF_EXPR: > return "&&"; > > so no, I don't think they are differentiated. Only because C does

[PATCH] testsuite: Relax line number match in gfortran.dg/pr95690.f90

actual line number is target dependent, allow any +! { dg-error "not a floating constant" "" { target *-*-* } 0 } -- 2.46.0 -- Andreas Schwab, SUSE Labs, sch...@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."

Re: [PATCH 3/3] [PR libfortran/101305] Fix ISO_Fortran_binding.h paths in gfortran testsuite

t one that is supposed to be picked up from the current directory? Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."

Re: [PATCH, Fortran] Revert to non-multilib-specific ISO_Fortran_binding.h

/* This is the IEEE 128-bit encoding, same as float128. */ #elif (LDBL_MANT_DIG == 113 \ && LDBL_MIN_EXP == -16381 \ -- 2.33.0 -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."

Re: [PATCH, Fortran] Revert to non-multilib-specific ISO_Fortran_binding.h

84 > > This looks like it matches existing Linux case already in place? gcc has its own , see gcc/include/float.h in the build directory. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."

Re: [PATCH, Fortran] Revert to non-multilib-specific ISO_Fortran_binding.h

4726333618164062e-16L > #define __LDBL_DENORM_MIN__ 7.46536864129530798597817535205257178e-4948L > #define __LDBL_HAS_DENORM__ 1 > #define __LDBL_HAS_INFINITY__ 1 > #define __LDBL_HAS_QUIET_NAN__ 1 > #define __LDBL_IS_IEC_60559__ 2 That looks like range of extended float, but rounded t

Re: [PATCH, Fortran] Revert to non-multilib-specific ISO_Fortran_binding.h

and that case was handled in ISO_Fortran_binding.h. Doesn't gcc always use its own float.h? Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."

Re: libgfortran.so SONAME and powerpc64le-linux ABI changes

Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."

Re: libgfortran.so SONAME and powerpc64le-linux ABI changes

versions of glibc, you are in for surprises, too. This isn't something new. There is no guarantee of API stability. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."

Re: [PATCH] doc: Remove @code wrapping of fortran option names [PR116801]

a different formatting), than as > "-free-line-length-". It makes it clear that there is a suffix to the > option. Whatever you feel like is the right solution, please make it constent throughout the manual. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47

Re: [PATCH] doc: Remove @code wrapping of fortran option names [PR116801]

On Sep 22 2024, Jakub Jelinek wrote: > On Sun, Sep 22, 2024 at 10:52:37PM +0200, Andreas Schwab wrote: >> On Sep 22 2024, Mikael Morin wrote: >> >> > @@ -370,7 +370,7 @@ Set the default accessibility of module entities to >> > @code{PRIVATE}. >> > Use-

Re: [PATCH] doc: Remove @code wrapping of fortran option names [PR116801]

On Sep 22 2024, Arsen Arsenović wrote: > Andreas Schwab writes: > >> On Sep 22 2024, Jakub Jelinek wrote: >> >>> On Sun, Sep 22, 2024 at 10:52:37PM +0200, Andreas Schwab wrote: >>>> On Sep 22 2024, Mikael Morin wrote: >>>> >>>>

Re: [PATCH] doc: Remove @code wrapping of fortran option names [PR116801]

var{n} > +@opindex ffixed-line-length-@var{n} Shouldn't all the @var{...} parts be dropped as well, throughout? -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."

Re: [PATCH] Fortran: fix crash with bounds check writing array section [PR117791]

not handled in switch [-Werror=switch] ../../gcc/fortran/trans-io.cc:2662:24: error: enumeration value 'EXPR_PPC' not handled in switch [-Werror=switch] cc1plus: all warnings being treated as errors make[3]: *** [Makefile:1203: fortran/trans-io.o] Error 1 -- Andreas Schwab, sch...@linu