On Thu, Sep 28, 2023 at 4:00 PM Toon Moene wrote:
> On 9/28/23 21:26, Jakub Jelinek wrote:
>
> > It is worse than that, usually the LTO format changes e.g. any time any
> > option or parameter is added on a release branch (several times a year)
> and
> > at other times as well.
> > Though,
On 9/28/23 21:26, Jakub Jelinek wrote:
It is worse than that, usually the LTO format changes e.g. any time any
option or parameter is added on a release branch (several times a year) and
at other times as well.
Though, admittedly GCC is the single package that actually could get away
with LTO
On Thu, Sep 28, 2023 at 09:03:39PM +0200, Toon Moene wrote:
> > > The full question of "lto-ing" run time libraries is more
> > > complicated than just "whether it works" as those who attended the
> > > BoF will recall.
> >
> > I didn't attend the Cauldron (but that discussion would have been
> >
On 9/28/23 07:33, Thomas Koenig wrote:
Hi Toon,
[ I wrote: ]
The full question of "lto-ing" run time libraries is more complicated
than just "whether it works" as those who attended the BoF will recall.
I didn't attend the Cauldron (but that discussion would have been
very interesting).
Hi Andre,
The patch looks fine to me. Since you mention it in the comment, is it
worth declaring the derived type 'foo' in a module and giving it a
final routine?
Thanks for the patch.
Paul
On Thu, 28 Sept 2023 at 13:45, Andre Vehreschild via Fortran
wrote:
>
> Hi all,
>
> attached patch
Hi,
> On 28 Sep 2023, at 14:56, Lingadahally, Vishakha (2023)
> wrote:
> Could you please let me know if there happens to be an update regarding how I
> might be able to resolve it?
when you are on an arm64 machine you need to add "-mcmodel=small” (applies to
Arm) instead of
Hi,
Could you please let me know if there happens to be an update regarding how I
might be able to resolve it?
Thanks!
Warm regards,
Vishakha
From: Iain Sandoe
Sent: 27 September 2023 08:35
To: Lingadahally, Vishakha (2023)
Cc: GCC Fortran
Subject: [EXT] Re:
Hi all,
attached patch fixes a crash in coarray programs when an allocatable derived
typed coarray was freed explicitly. The generated cleanup code did not take
into account, that the coarray may have been deallocated already. The patch
fixes this by moving the statements accessing components
On Thu, Sep 28, 2023 at 01:00:41PM +0200, Tobias Burnus wrote:
> I am not aware of any logigal/integer/real(+comples)/character kind > 16,
> except for this PPC one. And complex numbers are pairs of BT_REAL.
>
> Thus, I think that patch should be fine - except:
>
> > Does anything error earlier
(replace gcc@ by gcc-patches@; see
https://gcc.gnu.org/pipermail/gcc/2023-September/242591.html
and other emails in that thread)
On 28.09.23 11:51, Jakub Jelinek wrote:
On Thu, Sep 28, 2023 at 09:29:02AM +0200, Tobias Burnus wrote:
On 28.09.23 08:25, Richard Biener via Fortran wrote:
This
On Thu, Sep 28, 2023 at 09:29:02AM +0200, Tobias Burnus wrote:
> the following works for me. I have only tried a normal build (where it
> does silence the same warning) and not an LTO build and I just believed
> the comment - see attached patch. Comments?
>
> On 28.09.23 08:25, Richard Biener via
Hi all,
the following works for me. I have only tried a normal build (where it
does silence the same warning) and not an LTO build and I just believed
the comment - see attached patch. Comments?
On 28.09.23 08:25, Richard Biener via Fortran wrote:
This particular place in libgfortran has
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 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 -O3 -flto -flto-partition=none -static -o xlintstrfz zchkrfp.o
> > zdrvrfp.o zdrvrf1.o
14 matches
Mail list logo
