Re: Updated Sourceware infrastructure plans

On Thu, Apr 18, 2024 at 11:15 AM FX Coudert wrote: > > > I regenerate auto* files from time to time for libgfortran. Regenerating > > them has always been very fragile (using --enable-maintainer-mode), > > and difficult to get right. > > I have never found them difficult to regenerate, but if you

Re: [PATCH][stage1] Remove conditionals around free()

On Wed, Mar 1, 2023 at 11:31 PM Bernhard Reutner-Fischer via Fortran wrote: > > Hi! > > Mere cosmetics. > > - if (foo != NULL) > free (foo); > > With the caveat that coccinelle ruins replacement whitespace or i'm > uneducated enough to be unable to _not_ run the diff through > sed -e

Re: [PATCH 3/5] Fortran: Narrow return types [PR78798]

On Sun, Nov 13, 2022 at 1:47 AM Bernhard Reutner-Fischer via Fortran wrote: > --- a/gcc/fortran/arith.cc > +++ b/gcc/fortran/arith.cc > @@ -1135,7 +1135,7 @@ compare_complex (gfc_expr *op1, gfc_expr *op2) > strings. We return -1 for a < b, 0 for a == b and 1 for a > b. > We use the

Re: Handling of large stack objects in GPU code generation -- maybe transform into heap allocation?

On Fri, Nov 11, 2022 at 4:13 PM Thomas Schwinge wrote: > For example, for Fortran code like: > > write (*,*) "Hello world" > > ..., 'gfortran' creates: > The issue: the stack object 'dt_parm.0' is a half-KiB in size (yes, > really! -- there's a lot of state in Fortran I/O apparently). > Any

Re: Lowest i386 CPU Model with proper C++ atomics

On Fri, Sep 11, 2020 at 6:52 PM Joel Sherrill wrote: > > Hi > > Over at RTEMS, we ran into a case where the C++ atomics may not be right > for one of the lower level x86 models. We will investigate whether it can > be made right but this has led to the discussion of dropping older models > and

Re: [PATCH] Don't assume __secure_getenv is available

PING On Thu, Apr 27, 2017 at 9:55 PM, Janne Blomqvist wrote: > On Thu, Apr 27, 2017 at 9:50 PM, Janne Blomqvist > wrote: > [snip] > > And on top of that patch this simple typo fix: > > diff --git a/libgfortran/runtime/environ.c