Re: Test with an lto-build of libgfortran.

2023-09-28 Thread Tobias Burnus
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 /

Re: Test with an lto-build of libgfortran.

2023-09-28 Thread Jakub Jelinek via Gcc
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

MIPS Built-ins

2023-09-28 Thread Ильвир Низамов via Gcc
Hello! You may call me Ilvir. I got an issue while building U-Boot for MIPS platform, because of __builtin_mips_cache needs optimization flags (like -O2) while non-literal int passed in it ("int op" at example below). Example code: static inline void mips_cache(int op, const volatile void *addr) {

Re: Test with an lto-build of libgfortran.

2023-09-28 Thread Toon Moene
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).  I

Re: GCC workshop at university

2023-09-28 Thread David Malcolm via Gcc
On Wed, 2023-09-27 at 22:20 +0200, Benjamin Priour wrote: > Hi everyone, > > I'm in my final MSc year and figured after this weekend's Q&A > that I could replicate David's workshop on a smaller scale within my > university. > > Would that be doable/acceptable ? That sounds like a great idea. >

Re: Test with an lto-build of libgfortran.

2023-09-28 Thread Jakub Jelinek via Gcc
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 > >

Re: Test with an lto-build of libgfortran.

2023-09-28 Thread Toon Moene
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 in

Re: Test with an lto-build of libgfortran.

2023-09-28 Thread David Edelsohn via Gcc
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, admitt

gcc-11-20230928 is now available

2023-09-28 Thread GCC Administrator via Gcc
Snapshot gcc-11-20230928 is now available on https://gcc.gnu.org/pub/gcc/snapshots/11-20230928/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 11 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch

Re: Test with an lto-build of libgfortran.

2023-09-28 Thread Thomas Koenig via Gcc
Hi Jakub, 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. Hm, that makes LTO not very well suited for libraries... Though, admittedly GCC is the single package that act