On Wed, Sep 27, 2023 at 11:28 PM Richard Biener via Fortran
wrote:
>
> On Wed, Sep 27, 2023 at 11:48 PM Jeff Law via Fortran
> wrote:
> >
> >
> >
> > On 9/27/23 12:21, Toon Moene wrote:
> >
> > >
> > > The lto-ing of libgfortran did succeed, because I did get a new warning:
> > >
> > > gfortran
On Tue, Sep 26, 2023 at 11:39 PM Richard Biener via Fortran
wrote:
>
> On Tue, Sep 26, 2023 at 4:44 PM Lingadahally, Vishakha (2023)
> wrote:
> >
> > Dear GCC Team,
> >
> > I'm running Ubuntu 22 on my Mac virtually and my gfortran version is
> > 11.4.0. When I try to install a certain software
So the problem here is EXPAND_INTER_MACRO_16 expands to nothing if 16 byte FP
does not
exist but we still add a comma after it and that causes a build failure.
The same is true for EXPAND_INTER_MACRO_10 too.
Committed as obvious after a bootstrap and test on x86_64-linux-gnu and
On Wed, May 17, 2023 at 1:15 PM Larry Lemons via Fortran
wrote:
>
> Hello,
>
> I inherited a project where the customer wants us to re-build this ForTran
> application with a more modern compiler. I did some research and found that
> the GCC compiler probably has the most up to date compiler
On Tue, Nov 15, 2022 at 7:47 AM Martin Liška wrote:
>
> Hi.
>
> I've just pushed libsanitizer update that was tested on x86_64-linux and
> ppc64le-linux systems.
> Moreover, I run bootstrap on x86_64-linux and checked ABI difference with
> abidiff.
This broke hwasan on aarch64. See
On Fri, Apr 28, 2023 at 8:32 AM Jerry D via Fortran wrote:
>
> Hello all and gcc overseers,
>
> I received a notice that the MasterMost server providers decided to drop
> their free service. Unfortunate and understandable.
>
> I plan to contact the Open Software Lab folks at Oregon State
The problem here is we were outputing long_long instead of
"long long". This was just an oversight and a missing check.
Committed as obvious after a bootstrap/test on x86_64-linux-gnu.
gcc/fortran/ChangeLog:
* dump-parse-tree.cc (get_c_type_name): Fix "long_long"
type name to be
On Wed, Mar 1, 2023 at 3:52 PM Bernhard Reutner-Fischer
wrote:
>
> On Wed, 1 Mar 2023 14:59:44 -0800
> Andrew Pinski wrote:
>
> > On Wed, Mar 1, 2023 at 1:31 PM Bernhard Reutner-Fischer via Fortran
> > wrote:
> > >
> > > Hi!
> > >
> > > Mere cosmetics.
> > >
> > > - if (foo != NULL)
> > >
On Wed, Mar 1, 2023 at 1: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
On Wed, Jan 25, 2023 at 1:07 PM Ben Boeckel via Fortran
wrote:
>
> Hi,
>
> This patch series adds initial support for ISO C++'s [P1689R5][], a
> format for describing C++ module requirements and provisions based on
> the source code. This is required because compiling C++ with modules is
> not
On Mon, Jan 30, 2023 at 12:27 PM Harald Anlauf via Fortran
wrote:
>
> Dear Hackers,
>
> is there a way to check that a particular warning is emitted only
> once for a source code line instead of multiple times?
>
> It appears that by default dg-warn matches one or more times.
One example of how
On Sat, Nov 12, 2022 at 3:47 PM Bernhard Reutner-Fischer via
Gcc-patches wrote:
>
> gcc/ChangeLog:
>
> * value-range.cc (get_bound_with_infinite_markers): New static helper.
> (irange::as_string): New definition.
> * value-range.h: New declaration.
>
> ---
> Provide means
On Sun, Jan 9, 2022 at 1:46 PM Harald Anlauf via Fortran
wrote:
>
> Dear all,
>
> while working on a PR related to kind=4 character issues, I saw the
> following in gfortran.h:
>
>
> /* We need to store source lines as sequences of multibyte source
> characters. We define here a type wide
13 matches
Mail list logo
