inedocs/gfortran/Interoperability-Options.html
However the manpage has Interoperability section explicitly disabled
with "@c man end" ... "@c man begin ENVIRONMENT".
After digging into git log it seems that Interoperability section was
unintentionally added after this comment mar
From: Rimvydas Jasinskas
Date: Sat, 23 Dec 2023 18:59:09 +
Subject: Fortran: Add Developer Options mini-section to documentation
Separate out -fdump-* options to the new section. Sort by option name.
While there, document -save-temps intermediates.
gcc/fortran/ChangeLog:
* invoke.texi: Add
"Developer options" mini-section (as suggested by
Harald) and moving the -fdump-* options from "Options for debugging
your program or GNU Fortran" section.
Regards,
Rimvydas
From d313ccb110c5418260b667c5f289a249247de059 Mon Sep 17 00:00:00 2001
From: Rimvydas Jasinskas
Date: Wed,
Hello Bernhard,
On Fri, Feb 24, 2023 at 9:20 AM Bernhard Reutner-Fischer
wrote:
> > > * decl.cc: Add EXT_ATTR_NOINLINE, EXT_ATTR_NORETURN, EXT_ATTR_WEAK.
> > > * gfortran.h (ext_attr_id_t): Ditto.
> >
> > We had that discussion recently here..
> > Which of these are required to be recorded to th
e addressed in the future.
> Finally, please do not forget to CC patches to gcc-patches@
> so that others can see them.
Out of curiosity, what is the purpose of CC patches to gcc-patches
too? Attachments are even available in web mailing list too, like in:
https://gcc.gnu.org/pipermail/for
cks if the symbol is "imported at (1)" versus
"declared at (1)".
Regtested cleanly on x86_64-pc-linux-gnu.
Regards,
Rimvydas
From e5319c1733bca56be710c8cbce763fe459dfae73 Mon Sep 17 00:00:00 2001
From: Rimvydas Jasinskas
Date: Thu, 23 Feb 2023 12:59:57 +
Subject: For
Thank you Harald, for the feedback!
Attached is part2 patch for weak variables support. I'll post part3
patch for module-wide attribute support separately.
Best regards,
Rimvydas
From fb1cf60d3fd7c6aa2d9787bb3af86f18e0178bf7 Mon Sep 17 00:00:00 2001
From: Rimvydas Jasinskas
Date: Thu, 2
On Tue, Feb 14, 2023 at 9:55 PM Harald Anlauf wrote:
> >>> There is one thing I cannot test, which is the handling of weak symbols
> >>> on other platforms. A quick glance at the C testcases suggests that
> >>> someone with access to either an NVPTX or MingGW target might tell
> >>> whether that
way, including any
> of the common MPI implementations, so should we care about Ada?
I agree with you. I have removed SUPPORTS_WEAK check and fixed
indentation in v2.
Regtested cleany on x86_64-pc-linux-gnu.
Regards,
Rimvydas
From 42190ec551deab46e11ae9d5920a574ab7a366a3 Mon Sep 17 00:00:00
On Fri, Feb 10, 2023 at 11:07 PM Harald Anlauf via Fortran
wrote:
> I actually like the idea of supporting the suggested attributes,
> provided they work and behave the same way with and without LTO.
All these three declaration attributes apply the same regardless of
LTO, LTO just expands what opt
On Fri, Feb 10, 2023 at 10:24 AM Steve Kargl via Fortran
wrote:
> > would it be possible to extend gfortran attribute support to handle
> > NOINLINE too? Like: "!GCC$ ATTRIBUTES noinline :: ...".
>
> It looks to me like you are conflating three independent topics.
> What does NOINLINE have to do w
st regards,
Rimvydas
From 7a197623c2efb30e4ecf78ce650b6727eef5e60b Mon Sep 17 00:00:00 2001
From: Rimvydas Jasinskas
Date: Fri, 10 Feb 2023 04:34:12 +
Subject: Fortran: Add !GCC$ attributes NOINLINE,NORETURN,WEAK
gcc/fortran/ChangeLog:
* decl.cc: Add EXT_ATTR_NOINLINE, EXT_ATTR_NORETURN, EXT_ATTR_WEAK.
*
12 matches
Mail list logo
