Re: Fortran: Add range-based diagnostic

2024-10-18 Thread Jerry D
On 10/18/24 3:35 PM, Tobias Burnus wrote: This patch was motivated by David's talk at Cauldron – and by getting rather bad locations for some diagnostics, where I wanted to use the column number to ensure that all items are found. The main problem was a missing gobbling of spaces, but still rang

Re: How to document intrinsics with UNSIGNED arguments...

2024-10-18 Thread Steve Kargl
On Fri, Oct 18, 2024 at 09:51:21PM +0200, Thomas Koenig wrote: > Am 18.10.24 um 19:11 schrieb Thomas Koenig: > > Hello world, > > > > I am thinking how to add UNSIGNED to the documentation of the > > intrinsics.  Taking BGT, the alphabetically first one, one > > could > > ... send the e-mail too

Fortran: Add range-based diagnostic

2024-10-18 Thread Tobias Burnus
This patch was motivated by David's talk at Cauldron – and by getting rather bad locations for some diagnostics, where I wanted to use the column number to ensure that all items are found. The main problem was a missing gobbling of spaces, but still ranges are way nicer. As gfortran uses the comm

Re: [Patch] Fortran: Fix translatability of diagnostic strings

2024-10-18 Thread Jerry D
On 10/18/24 3:20 PM, Tobias Burnus wrote: *Patch ping* OK for trunk. Jerry Tobias Burnus wrote: I noticed that several diagnostic strings were not tagged as translatable. I fixed them by adding _ or G_ as prefix ( →gcc/ABOUT-GCC-NLS) and moved a single-use string to the message to make it

Re: [Patch] Fortran: Fix translatability of diagnostic strings

2024-10-18 Thread Tobias Burnus
*Patch ping* Tobias Burnus wrote: I noticed that several diagnostic strings were not tagged as translatable. I fixed them by adding _ or G_ as prefix ( →gcc/ABOUT-GCC-NLS) and moved a single-use string to the message to make it more readable. One error message did not quit fit the pattern, hen

Re: How to document intrinsics with UNSIGNED arguments...

2024-10-18 Thread Thomas Koenig
Am 18.10.24 um 19:11 schrieb Thomas Koenig: Hello world, I am thinking how to add UNSIGNED to the documentation of the intrinsics.  Taking BGT, the alphabetically first one, one could ... send the e-mail too early. What I had in mind was something like @node BGT @section @code{BGT} --- Bitwi

Re: Jubilado

2024-10-18 Thread Steve Kargl
On Fri, Oct 18, 2024 at 11:35:40AM +0200, Arjen Markus wrote: > > The current version of the standard is Fortran 2018 ... > The current version of the Fortran standard is ISO/IEC 1539-1:2023; more commonly known as Fortran 2023. -- Steve

How to document intrinsics with UNSIGNED arguments...

2024-10-18 Thread Thomas Koenig
Hello world, I am thinking how to add UNSIGNED to the documentation of the intrinsics. Taking BGT, the alphabetically first one, one could write

Re: Issue about buildpath introduced by -fintrinsic-modules-path option

2024-10-18 Thread ChenQi
On 10/18/24 14:17, Andrew Pinski wrote: On Thu, Oct 17, 2024 at 7:52 PM ChenQi wrote: Hi Fortran community, I recently got a buildpath issue when building libgfortran. I'm sending out email to this mailing list first, but if you think it's a bug instead of some expected behavior, please let me