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

> On 3 Mar 2023, at 23:11, Bernhard Reutner-Fischer via Fortran > wrote: > > On 2 March 2023 02:23:10 CET, Jerry D wrote: >> On 3/1/23 4:07 PM, Steve Kargl via Fortran wrote: >>> On Wed, Mar 01, 2023 at 10:28:56PM +0100, Bernhard Reutner-Fischer via >>> Fortran wrote: libgfortran/caf/

Re: What .dylib files does gfortran v 11.2.0 need on a Mac?

Hi Leigh > On 22 Jul 2023, at 19:20, Leigh House via Fortran wrote: > > I’ve not been able to get any output written to a file by a program I > compiled with gfortran v11.2.0 on my Mac. The Mac has MacOS Monterey > (v12.6.7). This seems like a simple problem, yet I’ve not been able to find a

Re: What .dylib files does gfortran v 11.2.0 need on a Mac?

Hi Leigh, > On 22 Jul 2023, at 20:05, Leigh House wrote: > > Thanks for your fast reply! > > My Mac is an intel iMac from 2019. That should be fine with “upstream” sources, should you decide to build from source (but that should not be necessary, there are several places providing gfortran

Re: gfortran: error: unrecognized argument in option '-mcmodel=medium'

> On 27 Sep 2023, at 08:25, Andrew Pinski via Fortran > wrote: > > 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 a

Re: gfortran: error: unrecognized argument in option '-mcmodel=medium'

> On 27 Sep 2023, at 08:33, Iain Sandoe wrote: > > > >> On 27 Sep 2023, at 08:25, Andrew Pinski via Fortran >> wrote: >> >> On Tue, Sep 26, 2023 at 11:39 PM Richard Biener via Fortran >> wrote: >>> >>> On Tue, Sep

Re: [EXT] gfortran: error: unrecognized argument in option '-mcmodel=medium'

tead of "-mcmodel=medium” (applies to Intel) Iain > > Thanks! > > Warm regards, > Vishakha > ____ > From: Iain Sandoe > Sent: 27 September 2023 08:35 > To: Lingadahally, Vishakha (2023) > Cc: GCC Fortran > Subject: [EXT] Re: gfortr

[PATCH] libgfortran: Fix up the autoreconf warnings.

egenerate. Signed-off-by: Iain Sandoe --- libgfortran/Makefile.am | 1431 +++--- libgfortran/Makefile.in | 9848 ++- 2 files changed, 4126 insertions(+), 7153 deletions(-) diff --git a/libgfortran/Makefile.am b/libgfortran/Makefile.am index 9f8a4f69863..8bef17

Re: [PATCH, gfortran] libgfortran: implement fpu-macppc for Darwin, support IEEE arithmetic

> On 14 Aug 2024, at 13:17, Sergey Fedorov wrote: > > > > On Wed, Aug 14, 2024 at 8:03 PM FX Coudert wrote: > > Thank you for responding. > > I have added a changelog (is this a correct way?). > > Content seems ok, lines are maybe too long. Check with > contrib/gcc-changelog/git_check_com

[pushed] libgfortran, configure : Adjust configure to autoconf-2.69

Hi As discussed on irc with Tobias… (I’ve included the changes to configure in this case since they are the only changes in the patch) bootstrapped on x86-64-linux-gnu pushed to releases/gcc-9. thanks Iain == It appears that at some point the configure file has been regenerated with auto

Fwd: Curious Behavior with Fortran gfortran-10.2-catalina.dmg on macOS Big Sur Version 11.4

At a first look, this does not seem to involve anything Darwin-specific (particularly, since this is x86_64, so nothing using experimental support). … perhaps someone here can see what the issue might be? Iain > Begin forwarded message: > > From: Lawrence Doctors > Subject: Curious Behavior wi

[PATCH] libgfortran : Use the libtool macro to determine libm availability.

Hi, A while ago had a report of build failure against a Darwin branch on the latest OS release. This was because (temporarily) the symlink from libm.dylib => libSystem.dylib had been removed/omitted. libm is not needed on Darwin, and should not be added unconditionally even if that is (mostly) h

Re: [PATCH] libgfortran : Use the libtool macro to determine libm availability.

> On 20 Aug 2021, at 08:52, Tobias Burnus wrote: > > On 20.08.21 09:34, Richard Biener via Fortran wrote: > >> On Thu, Aug 19, 2021 at 10:10 PM Iain Sandoe wrote: >>> libm is not needed on Darwin, and should not be added unconditionally >>> even if tha

Re: [PATCH] libgfortran : Use the libtool macro to determine libm availability.

> On 21 Aug 2021, at 23:18, Eric Gallager wrote: > > On Fri, Aug 20, 2021 at 3:53 AM Tobias Burnus wrote: >> >> On 20.08.21 09:34, Richard Biener via Fortran wrote: >> >>> On Thu, Aug 19, 2021 at 10:10 PM Iain Sandoe wrote: >>>> libm

Re: [PATCH] libgfortran : Use the libtool macro to determine libm availability.

> On 22 Aug 2021, at 09:44, Iain Sandoe wrote: > > > >> On 21 Aug 2021, at 23:18, Eric Gallager wrote: >> >> On Fri, Aug 20, 2021 at 3:53 AM Tobias Burnus >> wrote: >>> >>> On 20.08.21 09:34, Richard Biener via Fortran wrote:

Re: Executable on Apple M1 and Apple Intel

Hello Heiner. > On 29 Sep 2021, at 08:04, Heiner Veelken via Fortran > wrote: > This is my first post; kindly inform me, if I did anything wrong :-) > I am using gfortran (M1) from hpc.sourceforge.net > on my Apple Macbook Pro M1. I just create my > executable vi

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

> On 8 Oct 2021, at 07:35, Thomas Koenig via Fortran > wrote: > > > On 07.10.21 17:33, Jakub Jelinek wrote: >>> It will also be a compatibility issue if users have code compiled on a LE >>> system with GCC 11 and earlier with KIND=16, it will not link with GCC 12. >> libgfortran ABI changed

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

Hi Thomas, recognising that this is complex - the intent here is to see if there are ways to partition the problem (where the pain falls does depend on the choices made). perhaps: *A library (interface, name) *B compiler internals *C user-facing changes > On 8 Oct 2021, at 17:26, Thomas K

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

> On 8 Oct 2021, at 23:55, Thomas Koenig via Gcc wrote: > > > Hi Iain, > >>> Things get interesting for user code, calling a routine compiled >>> for double double with newer IEEE QP will result in breakage. >> That would not happen with the proposal above, since the library would >> have di

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

> On 9 Oct 2021, at 10:11, Thomas Koenig wrote: > > > On 09.10.21 01:18, Iain Sandoe wrote: >>> I meant the case where the user writes, with an old, KIND=16 is double >>> double compiler, >>> >>> subroutine foo(a) >>>real(k

Re: [Patch, fortran] PR117434 - [F08] gfortran rejects actual argument corresponding to procedure pointer dummy argument

Hi Folks. > On 5 Nov 2024, at 19:23, Harald Anlauf wrote: > > Hi Paul, > > Am 05.11.24 um 16:24 schrieb Paul Richard Thomas: >> Hi All, >> >> There is not much to say about the attached patch other than it is minimal >> :-) The testcases are probably a bit more than is strictly needed since th

Re: [pushed] doc, fortran: Add a missing menu item.

> On 27 Oct 2024, at 08:08, Thomas Koenig wrote: > > Am 27.10.24 um 00:15 schrieb Iain Sandoe: >> Tested on x86_64-darwin21 and linux, with makeinfo 6.7 pushed to trunk, >> thanks > For the record, makeinfo 6.8 did not show this as an error. Hmm that’s maybe a regres

Re: [patch, Fortran, doc] Update descriptions for UNSIGNED

> On 26 Oct 2024, at 22:41, Thomas Koenig wrote: > > Am 26.10.24 um 22:10 schrieb Iain Sandoe: >>> Pushed (4727bfb37701f3fef98a5f8b60dcd2daa82e8143). >> This seems to have broken —enable-languages=all bootstrap with >> /src-local/gcc-master/gcc/fortran/intr

[pushed] doc, fortran: Add a missing menu item.

exi: Add menu item for UINT. Signed-off-by: Iain Sandoe --- gcc/fortran/intrinsic.texi | 1 + 1 file changed, 1 insertion(+) diff --git a/gcc/fortran/intrinsic.texi b/gcc/fortran/intrinsic.texi index 0354704e4d0..f47fa3bbd5e 100644 --- a/gcc/fortran/intrinsic.texi +++ b/gcc/fortran/intrinsic.t

Re: [patch, Fortran, doc] Update descriptions for UNSIGNED

Hi Thomas > On 26 Oct 2024, at 18:28, Thomas Koenig wrote: > > Hi Steve, > >>> OK for trunk? >>> >> OK, but see below. > > Pushed (4727bfb37701f3fef98a5f8b60dcd2daa82e8143). This seems to have broken —enable-languages=all bootstrap with /src-local/gcc-master/gcc/fortran/intrinsic.texi:39:

Re: On pull request workflows for the GNU toolchain

> On 23 Sep 2024, at 15:33, Jonathan Wakely wrote: > > On Mon, 23 Sept 2024 at 14:36, enh wrote: >> >> it doesn't make the patch _management_ problem better ("now i have two >> problems"), but https://github.com/landley/toybox takes the "why not both?" >> approach --- you can use pull reque

[pushed] libgfortran: Fix bootstrap on targets without static_assert macro.

the keyword directly. tested on i686-darwin9 and x86_64-darwin18, without regressions, pushed to master as an obvious bootstrap fix (and as approved by FX). thanks Iain Signed-off-by: Iain Sandoe libgfortran/ChangeLog: * runtime/string.c (gfc_itoa): Use _Static_assert directly

Re: gfortran run on 64bit Mac ?

Hello David, > On 29 Jan 2022, at 11:14, dmainprice via Fortran wrote: > gfortran run on 64bit Mac ? Yes, gfortran has been running on (x86_64) 64bit Mac since macOS 10.6. > Any suggestions will F77 code run ? if it will compile with gfortran, then you could expect it to run, cheers Iain >

Re: gfortran static linking under OS X (was: Re: )

Hi Daniel, Tobias Burnus wrote: I am not sure whether it helps, but I want to point out that libm is the math library which is on Linux usually GLIBC and I assume on OS X it is provided by the OS vendor. actually part of libSystem (but, yes, provided by the vendor) On 19.03.21 21:22, D

Re: gfortran static linking under OS X (was: Re: )

Daniel Feenberg wrote: On Fri, 19 Mar 2021, Tobias Burnus wrote: This seems to be a OS X issue ? and I have no idea about OS X, but I found the following: https://github.com/fxcoudert/gfortran-for-macOS/issues/12 It is certainly an OS X issue. Actually, it’s a gfortran issue. The

Re: gfortran static linking under OS X (was: Re: )

Daniel Feenberg wrote: On 3/19/21, Iain Sandoe wrote: On Fri, 19 Mar 2021, Tobias Burnus wrote: you should be able to work around this without changing the compiler or rebuilding it, %rename lib liborig *lib: -lquadmath -lm %(libgcc) %(liborig) change the last line line to : *lib

Re: Installation in MAC M1

Hello Soumyadip, > On 5 Jul 2021, at 07:18, Soumyadip Sahoo via Fortran > wrote: > > HII, I am soumyadip ,from India , I want to install fortran compiler in my > Mac Pro M1 processor . Please give me proper way to installation , it will be > very helpful. GCC (and therefore gfortran) suppor

Re: Error in installing home brew

Hi Soumyadip, this mailing list is primarily for discussion of gfortran development - > On 5 Jul 2021, at 08:05, Soumyadip Sahoo via Fortran > wrote: > > Here is the error :- > soumyadipsahoo@soumyadips-MacBook-Pro ~ % sudo apt install—gfortran — You will need to file problems/errors directl

Re: [Patch v3 Fortran] Fix c_float128 and c_float128_complex on targets with 128-bit long double.

Hi Folks > On 11 Aug 2021, at 11:55, Segher Boessenkool > wrote: > On Tue, Aug 10, 2021 at 04:46:11PM -0600, Sandra Loosemore wrote: >> OK. I used your wording verbatim for the first one. For the second >> one, I'm still pretty confused as I think it is at least theoretically >> possible on