On Fri, Mar 3, 2023 at 10:14 PM Jerry D via Fortran wrote:
> I am certainly not a C++ expert but it seems to me this all begs for
> automatic finalization where one would not have to invoke free at all.
> I suspect the gfortran frontend is not designed for such things.
+1 for RAII
On Fri, Jan 20, 2023 at 10:21 PM Jerry DeLisle via Fortran
wrote:
>
> Hi all,
>
> Similar to a patch I committed a while ago for Cygwin, the attached
> patch allows it to pass on the mingw version of gfortran.
>
> It is trivial.
>
> Ok for trunk?
>
> Regards,
>
> Jerry
ping
On Sun, Jan 29, 2023 at 2:37 PM Jerry D via Fortran wrote:
>
> I had this show up today. I have no idea what this is about.
>
> Please advise.
I assume the buildbot thinks that
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=8011fbba7baa46947341ca8069b5a327163a68d5
broke the build, but I fail to se
On Sat, Jan 21, 2023, 18:59 Jerry D via Fortran wrote:
>
> Proposed ChangeLog entry using git gcc-commit-mklog:
>
> Author: Jerry DeLisle
> Date: Sat Jan 21 15:47:19 2023 -0800
>
> Revise the line end tests to pass on certain windows test environments
> which inject spurious /r chara
On Thu, Jan 19, 2023, 13:33 Bernhard Reutner-Fischer
wrote:
> On 19 January 2023 13:52:55 CET, NightStrike via Fortran <
> fortran@gcc.gnu.org> wrote:
>
> >You can, and people naturally do this, and I think it's great, but
> >there's usually a response
On Thu, Jan 19, 2023 at 7:46 AM Toon Moene wrote:
>
> On 1/19/23 13:28, NightStrike via Fortran wrote:
>
> > On Thu, Jan 19, 2023, 00:01 Benson Muite via Fortran
> > wrote:
> >
> >> The GCC workflows is quite different from other open source projects
>
On Thu, Jan 19, 2023, 00:01 Benson Muite via Fortran
wrote:
> The GCC workflows is quite different from other open source projects
> being primarily email based and not using a bug tracker.
>
There's a bug tracker. I think you mean there isn't a patch tracker (or at
least not a system where you
On Tue, Dec 13, 2022, 03:10 Janne Blomqvist via Fortran
wrote:
> But in general, yes, I do think IRC is showing its age in an
> increasingly multi-device and mobile world.
>
Tools like irccloud help here. I guess that doesn't qualify as open source
though.
>
On Fri, Dec 23, 2022 at 7:00 PM Jonathan Yong via Gcc-patches
wrote:
>
> On 12/22/22 12:28, i.nix...@autistici.org wrote:
> > On 2022-12-22 12:21, Jonathan Yong wrote:
> >
> > hello,
> >
> >> On 12/16/22 19:20, Eric Botcazou wrote:
> The libgcc parts look reasonable to me, but I can't approve
On Fri, Dec 16, 2022 at 1:44 AM Thomas Koenig wrote:
>
> On 16.12.22 03:20, NightStrike via Fortran wrote:
>
> > When I run the testsuite under wine, I'm getting a lot of ANSI escape
> > sequences. We had fixed this long ago, but it seems to be back. Any
> >
When I run the testsuite under wine, I'm getting a lot of ANSI escape
sequences. We had fixed this long ago, but it seems to be back. Any
idea what I should change in my configuration to have this not happen?
This is for build=host=x86_64-pc-linux-gnu and
target=x86_64-w64-mingw32, with the test
On Wed, Apr 21, 2021 at 6:17 AM Tobias Burnus wrote:
>
>
> >> On Wed, 21 Apr 2021 02:34:43 -0400
> >> NightStrike via Fortran wrote:
> >>> When linking with -static-libgfortran, I get warnings from ld of the form
> >>> "ld: warning: -z ig
On Wed, Apr 21, 2021 at 6:06 AM Bernhard Reutner-Fischer
wrote:
>
> On Wed, 21 Apr 2021 05:29:28 -0400
> NightStrike wrote:
>
> > On Wed, Apr 21, 2021 at 4:59 AM Bernhard Reutner-Fischer
> > wrote:
> > > On Wed, 21 Apr 2021 02:34:43 -0400
> > > NightStr
On Wed, Apr 21, 2021 at 4:59 AM Bernhard Reutner-Fischer
wrote:
> On Wed, 21 Apr 2021 02:34:43 -0400
> NightStrike via Fortran wrote:
>
> > When linking with -static-libgfortran, I get warnings from ld of the form
> > "ld: warning: -z ignore ignored" and &quo
When linking with -static-libgfortran, I get warnings from ld of the form
"ld: warning: -z ignore ignored" and "ld: warning: -z record ignored". I
can't find those -z options documented anywhere. Why is gfortran adding
them?
15 matches
Mail list logo
