On Wed, Apr 16, 2025 at 04:44:23AM +, ZAPART CHRISTOPHER ANDREW wrote:
>
> After a recent upgrade from Fedora 41 to 42 the gfortran got updated from 14
> to 15.0.1:
>
> [chris@fedora FITSWEBQLSE]$ gfortran --version
> GNU Fortran (GCC) 15.0.1 20250329 (Red Hat 15.0.1-0)
>
> The new version
On Mon, Apr 07, 2025 at 02:42:10PM +0800, Gwen Fu wrote:
> Thanks for your reply !
> >The word "parameter" has very a specific meaning in Fortran. The
> >entity that is passed into a function or subroutine is an "actual
> >argument". The entity within the functions associated with the
> >"actual ar
On Sat, Apr 05, 2025 at 03:16:45PM +0800, Gwen Fu wrote:
> My doubt :
> 1.Does the compilation option only need to support fortran versions above
> 9, o5r does it also need to support fortran 77?
gfortran started life as a Fortran 95 compiler. It should
support anything that is Fortran 95 or late
On Thu, Mar 27, 2025 at 03:43:49PM +, Yuao Ma wrote:
>
> Thanks for sharing more details. I’ve realized that implementing half-cycle
> trig functions can be quite tricky. If I get the chance to refine the patch,
> I’d like to go through each function one by one (if the reviewers don’t mind),
>
On Fri, Apr 04, 2025 at 02:40:06AM -0400, NightStrike wrote:
>
> Is this email list still active? :)
Are you subscribed to the list?
First reply:
https://gcc.gnu.org/pipermail/fortran/2025-March/061963.html
Second reply:
https://gcc.gnu.org/pipermail/fortran/2025-March/061981.html
--
Steve
On Sun, Mar 30, 2025 at 02:06:31PM +, Yuao Ma wrote:
>
> I have uploaded a draft proposal for the 'Fortran – 2018/202x' project to the
> platform. You can also find a PDF version at this Google Drive link:
> https://drive.google.com/file/d/1cSRPuWpXWHMwHdNItQluEYspLfylqZcU.
I rarely follow ra
On Fri, Mar 28, 2025 at 02:02:03PM -0400, NightStrike wrote:
>
> Should I open a bugzilla PR about this?
>
Submit the 3-character patch to fix the error to
point to -fallow-invalid-boz instead of the negative
form -fno-allow-invalid-boz, which seems to have
led to a manner of confusion.
Other th
starting point for the project!
>
> Yuao
> ____
> From: Steve Kargl
> Sent: Tuesday, March 25, 2025 2:25
> To: Yuao Ma
> Cc: fortran@gcc.gnu.org
> Subject: Re: GSoC Fortran – 2018/202x – Inquiry About Project Scope
>
> I've already written a prototype of the half-cycl
TL;DR version: fix your code.
On Tue, Mar 25, 2025 at 11:04:52AM -0400, NightStrike wrote:
> Between GCC 9 and 10, the following code now errors out:
>
Did you read the Release Notes for 10.1? Under the Fortran header:
The handling of a BOZ literal constant has been reworked to provide
On Tue, Mar 25, 2025 at 08:34:51PM +0800, Gwen Fu wrote:
> I found out that "-fcheck=*" is an option for runtime checking, but the
> relevant options are commented out.
> OPT_fcheck_ = 1070,/* -fcheck= */
> /* OPT_fcheck_assert = 1071, *//* -fcheck=assert */
On Mon, Mar 24, 2025 at 09:40:38PM +0100, Thomas Koenig wrote:
>
> Regression-tested. Again no test case because I don't know
> how. During testing, I also found that vtabs were dumped,
> this is also corrected.
>
> OK for trunk?
Thanks for working on this, but ...
>
> /* This section deals
On Mon, Mar 24, 2025 at 08:46:50PM +0200, Janne Blomqvist wrote:
> On Mon, Mar 24, 2025 at 8:25 PM Steve Kargl
> wrote:
> >
> > I've already written a prototype of the half-cycle trig
> > functions.
> >
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=1131
I've already written a prototype of the half-cycle trig
functions.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152
There are two issues that need to be address. First, some
operating systems provide half-cycle trig functions in their
libm. The initial patch tries to use libm functions if
f
On Sun, Mar 23, 2025 at 10:09:46AM +0100, Thomas Koenig wrote:
> Hi Paul,
>
> > By the way, the standard just specifies integer for 'dim' in reduce,
> > which I take to mean it should be default_integer_kind.
>
> Hmm... I'm not sure that this is actually the case; I believe it
> can actually be a
On Wed, Mar 19, 2025 at 11:08:58PM +0100, Harald Anlauf wrote:
>
> the attached patch addresses an actually very long-standing issue
> with bogus bounds checks for components of nested derived types in
> assignments when an intermediate level has the POINTER attribute
> instead of the ALLOCATABLE
On Sat, Mar 08, 2025 at 01:52:06PM +0100, Thomas Koenig wrote:
>
> the attached patch fixes an ICE regresseion where undo state was not
> handled properly when generating formal from actual arguments, which
> occurred under certain conditions with the newly introduced
> -Wexternal-argument-mismatc
Andre,
Here's a bit of wordsmith. I removed the abbreviation "Esp."
I'm not sure if there is additional markup needed; especially,
with the "-fcoarray=single" I inserted.
Coarray support has been reworked to allow access to components
in derived types that have not been compiled with coarray
On Thu, Mar 06, 2025 at 10:49:08PM +0100, Harald Anlauf wrote:
>
> Thanks for the speedy review!
>
It was a bit easier than normal. After I submitted
the PR, I started to poke around in fortran/resolve.cc
to see if I could deal with the issue. I saw that you
grab the PR last night, and left yo
On Thu, Mar 06, 2025 at 10:04:08PM +0100, Harald Anlauf wrote:
>
> this patch fixes an interesting regression that prevented substring
> bounds checks from being generated if the substring start was not a
> variable, but rather a constant or an expression.
>
> The fix I chose turned out to be a l
On Mon, Mar 03, 2025 at 03:58:24PM +0100, Andre Vehreschild wrote:
>
> attached patches fix a 12-regression, when a caf token is requested from an
> abstract class-typed dummy. The token was not looked up in the correct spot.
> Due the class typed object getting an artificial variable for direct d
On Sat, Mar 01, 2025 at 03:56:21PM +0100, Harald Anlauf wrote:
>
> the attached patch fixes a front-end memleak that is seen when
> running f951 under valgrind and while parsing invalid uses of
> NULLIFY.
>
> I had this in my tree for some time without any problems, in an
> attempt to further red
On Sun, Feb 16, 2025 at 09:36:20AM +0100, Thomas Koenig wrote:
>
> this patch is a variation of Jakub's patch in the PR, which
> avoids overflow on the mask used for exponentiation and
> fixes unsigned HOST_WIDE_INT. I tried testing this on
> a POWER machine, but --with-build-config=bootstrap-ubs
On Fri, Feb 07, 2025 at 09:31:12PM +0100, Harald Anlauf wrote:
>
> Regtested on x86_64-pc-linux-gnu. OK for mainline?
>
Looks reasonable.
> While it is a really old bug but wrong code, I'd like to backport
> this also at least to 14-branch. Any reservations?
If it passes regression testing,
On Mon, Feb 03, 2025 at 01:34:09PM -0500, Andi McClure wrote:
>
> open(10,file=path,access='stream',form='unformatted',action='read',iostat=file_error)
You opened the file with form='unformatted'.
> READ (iu,"()", ADVANCE='NO', POS=file_pos) ! iu is file unit
You then try to use a format statem
> Summary: It is my opinion from the FORTRAN 2023 spec that the first test
> program above should have worked and the additional steps in the second
> test program should not have been necessary. Have I misread the spec, is
> there something wrong with my code, or have I identified a bug in gfortra
On Sat, Feb 01, 2025 at 09:49:17PM +0100, Harald Anlauf wrote:
> Am 01.02.25 um 21:03 schrieb Steve Kargl:
> > On Sat, Feb 01, 2025 at 07:25:51PM +0100, Harald Anlauf wrote:
> > >
> > > the attached patch downgrades different constant character lengths in an
> >
On Sat, Feb 01, 2025 at 07:25:51PM +0100, Harald Anlauf wrote:
>
> the attached patch downgrades different constant character lengths in an
> array constructor from a GNU to a legacy extension, so that users get a
> warning with -std=gnu. We continue to generate an error when standard
> conforman
On Mon, Jan 13, 2025 at 01:23:58AM +0100, Manfred Schwarb wrote:
> Am 11.01.25 um 07:36 schrieb Steve Kargl:
> > On Fri, Jan 10, 2025 at 05:19:34PM +, Paul Richard Thomas wrote:
> >>
> >> As of today, Gerhard Steinmetz has no fewer than 33 regressions to his name
&g
On Fri, Jan 10, 2025 at 05:19:34PM +, Paul Richard Thomas wrote:
>
> As of today, Gerhard Steinmetz has no fewer than 33 regressions to his name
> out of a total of 54 for fortran and libgfortran. It's time that some of
> these bugs are swatted, I think :-)
>
PR 70949 appears to have been fi
On Fri, Jan 10, 2025 at 05:19:34PM +, Paul Richard Thomas wrote:
>
> As of today, Gerhard Steinmetz has no fewer than 33 regressions to his name
> out of a total of 54 for fortran and libgfortran. It's time that some of
> these bugs are swatted, I think :-)
>
This patch fixes PR71844. As th
On Fri, Jan 10, 2025 at 09:41:13PM +, Harald Anlauf wrote:
>
> There is one question to the reviewer(s), or those knowing better
> than me how to handle IEEE infinity and NaN: with -Ofast, I needed
> to add "-fno-finite-math-only" to the new testcase
> gfortran.dg/ieee/out_of_range.f90, as the
On Fri, Jan 10, 2025 at 05:19:34PM +, Paul Richard Thomas wrote:
>
> As of today, Gerhard Steinmetz has no fewer than 33 regressions to his name
> out of a total of 54 for fortran and libgfortran. It's time that some of
> these bugs are swatted, I think :-)
>
When I was much more active in a
On Wed, Jan 08, 2025 at 10:33:53AM +0100, Jakub Jelinek wrote:
>
> As mentioned in the PR, there is a *.mod incompatibility between GCC 14 and
> GCC 15, at least when using iso_c_binding or iso_fortran_env intrinsic
> modules, because new entries have been added to those modules in the middle,
> c
On Tue, Jan 07, 2025 at 03:28:31PM +0100, Thomas Koenig wrote:
> Hello world,
>
> the attached patch does what it says in the ChangeLog entry.
>
> Tested with "make dvi" and "make pdf".
>
> OK for trunk?
>
OK.
--
Steve
I'm ok withi your patch. It seems to also catch PR113928.
You may want to give others a chance to chime in.
--
steve
On Thu, Dec 19, 2024 at 09:34:38PM +, Harald Anlauf wrote:
>
> the check for potential aliasing of lhs and rhs currently shortcuts
> if the types differ. This is a problem
On Wed, Dec 18, 2024 at 10:09:26AM -0800, Jerry D wrote:
> On 12/18/24 4:11 AM, Harald Anlauf wrote:
> > Hi Steve,
> >
> > thanks for the draft patch.
> >
> > I haven't looked close enough, but you may have to add support
> > for 'asis' being an optional dummy variable. The following
> > example
On Wed, Dec 18, 2024 at 01:11:14PM +0100, Harald Anlauf wrote:
>
> I haven't looked close enough, but you may have to add support
> for 'asis' being an optional dummy variable. The following
> example crashes here with a segfault:
>
(program snipped for brevity)
>
> There are other intrinsics
All,
First, I would like to thank both mikael and fx for providing
help in my debugging of the in-lining in trans-intrinsic.cc.
It seems I have forgotten much of what I once knew about trees.
I have attached a patch that implements F2023 F_C_STRING() to
https://gcc.gnu.org/bugzilla/show_bug.cgi?
On Mon, Dec 16, 2024 at 04:53:42AM -0800, Damian Rouson wrote:
> including automatic GPU offloading. Then a few months ago, the death blow
> that I couldn’t work around was robust support for kind type parameters.
>
gfortran doesn't have robust kind type parameters?
% cat xx.f90
program foo
I have taken the attempt at inlining f_c_string()
as far as I can. The WIP patch is attached to the
PR along with the final issue that I cannot resolve.
If anyone wants to finish the patch, feel free to
do so.
--
Steve
On Fri, Dec 13, 2024 at 03:09:57PM -0800, Steve Kargl wrote:
> On Fri, Dec 13, 2024 at 10:54:03PM +0100, Mikael Morin wrote:
> > Le 13/12/2024 à 21:55, Steve Kargl a écrit :
> > > On Mon, Dec 09, 2024 at 06:39:19PM -0800, Steve Kargl wrote:
> > > >
> > > &
On Fri, Dec 13, 2024 at 10:54:03PM +0100, Mikael Morin wrote:
> Le 13/12/2024 à 21:55, Steve Kargl a écrit :
> > On Mon, Dec 09, 2024 at 06:39:19PM -0800, Steve Kargl wrote:
> > >
> > > I've an almost complete implementation of F_C_STRING,
> > > but need
On Mon, Dec 09, 2024 at 06:39:19PM -0800, Steve Kargl wrote:
>
> I've an almost complete implementation of F_C_STRING,
> but need a bit of insight on the inlining that I'm
> trying to implement. In pseudo-code, F_C_STRING is
>
> case 1. f_c_string(string)
FX,
You're likely correct that the creation of an expression for
c_null_char is overkill. I copied the code from gfc_conv_concat_op()
in trans-expr.cc to get the 'f_c_string(s) -> trim(s) // c_null_char'.
This was the motivation of creating a string. If I look at the
-fdump-tree-orginal for
On Tue, Dec 10, 2024 at 09:05:02AM +0100, FX Coudert wrote:
> Hi Steve,
>
> > I've an almost complete implementation of F_C_STRING,
> > but need a bit of insight on the inlining that I'm
> > trying to implement.
>
> Maybe I can help. Can you send in your current patch?
>
FX,
I've attached the
All,
I've an almost complete implementation of F_C_STRING,
but need a bit of insight on the inlining that I'm
trying to implement. In pseudo-code, F_C_STRING is
case 1. f_c_string(string) = trim(string) // c_null_char
case 2. f_c_string(string, asis=.false.) = trim(string) // c_n
On Mon, Nov 25, 2024 at 10:05:49PM +, Harald Anlauf wrote:
> Dear all,
>
> the attached patch fixes an ICE when passing an inquiry reference of a complex
> array to an assumed-rank dummy argument by terminating the search for the
> array reference before we hit the inquiry reference. (The arr
On Fri, Nov 01, 2024 at 01:01:39PM +0100, Mikael Morin wrote:
> Le 30/10/2024 à 23:00, Harald Anlauf a écrit :
> >
> > given that Jakub changed lots of whitespace in r15-4624-g50332a4fdd3243,
> > you may want to rebase your patches onto HEAD of trunk.
> >
> > May I also suggest to attach the patc
On Sat, Nov 16, 2024 at 02:55:11PM +0100, Thomas Koenig wrote:
>
> Steve found a test case where unsigned constants were not handled
> in a module. Single-line patch committed as obvious and simple,
> r15-5341-g66096151afc6631f8f2a3458b154c5daa822b963 .
>
> Best regards
>
> Thomas
>
Than
On Wed, Nov 13, 2024 at 05:33:20PM +0100, Thomas Koenig wrote:
> Am 13.11.24 um 15:55 schrieb Toon Moene:
> >
> > Since the Fortran 95 Standard it does (in the current Standard: 7.4.3.2
> > Real type):
> >
> > The real type includes a zero value. Processors that distinguish between
> > positive a
On Fri, Nov 01, 2024 at 10:00:29AM +0100, Thomas Koenig wrote:
>
> during testing, I noticed that parameters of the form
> - mod(u1,u2) were rejected with an unknown type. The fix
> is straightforward, but required an adjustment to another
> test case.
>
> Regression-tested. OK for trunk?
>
Ye
On Wed, Oct 30, 2024 at 04:41:40PM +, Paul Richard Thomas wrote:
> This wrinkle to PR115700 came about because the associate-name string
> length was not being initialized, when an array selector had a substring
> reference with non-constant start or end. This, of course, caused
> subsequent re
On Tue, Oct 29, 2024 at 04:47:24PM +0900, Kazuyoshi Furutaka wrote:
> I've filed a report, and immediately it was marked as a duplicate
> of https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101826
>
Thanks. I was unaware that someone had reported a
similar bug report. Sorry about the extra effort
On Mon, Oct 28, 2024 at 06:00:18PM +0900, Kazuyoshi Furutaka wrote:
> Dear gfortran experts...
>
> The attached program runs OK, but `ptype`ing using gdb
> on the deferred-length character array returns empty(?)
> result, as the following (the results for integer and
> real arrays are correct ):
>
On Sat, Oct 26, 2024 at 05:16:54PM +0200, Thomas Koenig wrote:
>
> OK for trunk?
>
OK, but see below.
> +@item @code{SUM}, @pxref{SUM}
> +@item @code{TRANSPOSE}, @pxref{TRANSPOSE}
> +@item @code{TRANSFER}, @pxref{TRANSFER}
> @end itemize
> +
> +The following intrincis are enabled with @option{
On Thu, Oct 24, 2024 at 07:46:28PM +0200, Thomas Koenig wrote:
>
> Peter Klausler noted in the discussion on github that Sun Fortran,
> from which the UNSIGNED proposal was drawn, used UNSIGNED instead
> of UINT for conversion of other types to UNSIGNED
> (see https://docs.oracle.com/cd/E19205-01/
On Thu, Oct 24, 2024 at 10:22:29PM +0200, Thomas Koenig wrote:
>
> > I'll note that match.cc(gfc_match_type_spec) has to deal with
> > REAL as a possible intrinsic function. See the comment
> >
> >/* REAL is a real pain because it can be a type, intrinsic subprogram,
> > or list item i
On Sat, Oct 19, 2024 at 05:38:30PM +, Wyche, George G
PW wrote:
>
> My Fortran project is based on -std=f2008. The GNU Fortran (For GCC version
> 15.0.0) manual's 8.260 STAT example does not link if -std=f2008 is on the
> command line: gfortran -std=f2008 test_st
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
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
On Sun, Oct 06, 2024 at 07:16:18PM +1100, John Campbell wrote:
>
> I can confirm that the bug is not evident in equation.com's Gfortran 11.1.0
This is your problem.
> and earlier, but is present from Gfortran 11.3.0.
Program seems to wo
On Sat, Sep 28, 2024 at 08:32:00PM +0200, Thomas Koenig wrote:
> Hello world,
>
> here's another small patch for FINDLOC for unsigned.
>
> OK for trunk?
>
OK. Other than UNSIGNED being a new experimental feature,
this patch almost qualifies as "Obvious".
--
Steve
OK. Thanks for the patch.
--
steve
On Sat, Sep 28, 2024 at 09:33:20AM +0200, Thomas Koenig wrote:
>
> this patch, consisting almost entirely of the test cases, implements
> CSHIFT and EOSHIFT for unsigneds.
>
> OK for trunk?
>
> Implement CSHIFT and EOSHIFT for unsigned.
>
> gcc/for
On Fri, Sep 27, 2024 at 08:12:01PM +0200, Andre Vehreschild wrote:
>
> the testcase is in the coarray directory, where tests are executed mit
> -fcoarray=single and lib. I don't know about none. Because the code stops
> compiling when it encounters a coarray with no single or lib. Therefore I
> su
On Fri, Sep 27, 2024 at 03:20:43PM +0200, Andre Vehreschild wrote:
>
> attached patch fixes a runtime issue when a coarray was passed as
> parameter to a procedure that was itself a parameter. The issue here
> was that the coarray was passed as array pointer (i.e. w/o descriptor)
> to the function
On Sat, Sep 14, 2024 at 11:02:42AM -0700, Steve Kargl wrote:
>
> While I understand the intent of 'positive form' vs 'negative form', the
> above might be clearer as
>
>Usage of intrinsics can be implemented either by generating a call
>to the libgf
On Fri, Sep 13, 2024 at 12:27:07PM +0200, Mikael Morin wrote:
> >
> > gcc/fortran/ChangeLog:
> >
> > * invoke.texi(finline-intrinsics): Document new flag.
> > * lang.opt (finline-intrinsics, finline-intrinsics=,
> > fno-inline-intrinsics): New flags.
> > * options.cc (gfc_post_opt
OK. Sorry about dropping the balli on a review.
I thought it had already been approved and committed.
--
steve
On Fri, Sep 13, 2024 at 12:19:48PM +0200, Mikael Morin wrote:
> Ping:
>
> https://gcc.gnu.org/pipermail/fortran/2024-July/060640.html
>
> Maybe I could argue that I can self approve,
, relative to F2003, and I
> suggest that, in memory of Reinhold, this continue as a DIN
> proposal. @Thomas, are you willing to carry this forward or should I
> transfer it to being a UK proposal?
>
> Best regards
>
> Paul
>
>
> On Mon, 9 Sept 2024 at 18:34, Steve Kargl
&
On Mon, Sep 09, 2024 at 12:26:53AM -0700, Damian Rouson wrote:
> On Sat, Sep 7, 2024 at 22:26 Steve Kargl
> wrote:
>
> > On Sat, Sep 07, 2024 at 08:17:42PM -0700, Jerry D wrote:
> >
> >
> > I personally would like to see -std=f2023 made the default.
>
>
On Sat, Sep 07, 2024 at 08:17:42PM -0700, Jerry D wrote:
> Steve and others
>
> We continue to run into issues with PRs like this. I would like to close
> these out. I completely hate the mechanisms we have for the options. Why?
> Because every time I look at it I have to think it through ten w
On Sun, Aug 18, 2024 at 12:10:18PM +0200, Thomas Koenig wrote:
> Hello world,
>
> this version of the patch includes DOT_PRODUCT, MATMUL and quite
> a few improvements for simplification.
>
All,
I have gone through Thomas's current patch and sent a
few emails with comments to him. To keep thin
On Thu, Sep 05, 2024 at 09:07:20AM +0200, Thomas Koenig wrote:
> Ping (a little bit)?
>
> With another weekend coming up, I would have some time to
> work on incorporating any feedback, or on putting in
> more intrinsics.
>
Last comment as I've made it to the end of the patch.
Your testcases ar
On Thu, Sep 05, 2024 at 09:07:20AM +0200, Thomas Koenig wrote:
> Ping (a little bit)?
>
> With another weekend coming up, I would have some time to
> work on incorporating any feedback, or on putting in
> more intrinsics.
>
In the documentation, you have
+Generally, unsigned integers are only p
ault) to a legacy extension (warning by default).
>
> The feature is tested in at least 4 gfortran testcases. I adjusted
> the pattern of one of these tests to check for the downgrade.
>
> Regtested on x86_64-pc-linux-gnu. OK for mainline?
>
> Thanks,
> Harald
>
>
On Fri, Aug 30, 2024 at 06:46:47PM +0200, Harald Anlauf wrote:
> Am 30.08.24 um 18:33 schrieb Steve Kargl:
> > On Thu, Aug 29, 2024 at 10:05:35PM +0200, Harald Anlauf wrote:
> > >
> > >
> > > Should we downgrade this extension to GFC_STD_LEGACY?
> >
On Thu, Aug 29, 2024 at 10:05:35PM +0200, Harald Anlauf wrote:
>
> Am 29.08.24 um 21:53 schrieb Steve Kargl:
> > Thanks for the patch. If you have not already opened a new PR for the
> > other issue with C8107, I'll open one later today. It's likely that
> > w
Thanks for the patch. If you have not already opened a new PR for the
other issue with C8107, I'll open one later today. It's likely that
we need to check the namelist-group-name for USE association in
match.cc:gfc_match_namelist.
Hmmm, it seems we already catch the error, but accept it as an
ex
On Tue, Aug 27, 2024 at 06:46:08PM +0200, Thomas Koenig wrote:
> Steve,
>
> > On Sun, Aug 18, 2024 at 12:10:18PM +0200, Thomas Koenig wrote:
> > >
> > > this version of the patch includes DOT_PRODUCT, MATMUL and quite
> > > a few improvements for simplification.
> >
> > Thomas,
> >
> > Your upd
On Wed, Aug 21, 2024 at 12:17:46PM +0200, Andre Vehreschild wrote:
>
> attached small patch removes a VIEW_CONVERT that I erroneously inserted during
> patching pr110033. PR86468 fixes the (co-)rank computation and therefore this
> VIEW_CONVERT is IMO obsolete. I think it may cause hard to find ru
On Sun, Aug 18, 2024 at 12:10:18PM +0200, Thomas Koenig wrote:
>
> this version of the patch includes DOT_PRODUCT, MATMUL and quite
> a few improvements for simplification.
Thomas,
Your updated patch applied cleanly on top-of-tree gcc.
Bootstrap and regression testing on amd64-*-freebsd
comple
On Thu, Aug 08, 2024 at 11:09:10AM +0200, Mikael Morin wrote:
>
> These patches are about inlining, there is no manipulation of the parse
> tree. So I would rather use a separate option (-finline-intrinsics?).
I've only followed the discussion from afar, but gcc already supports
a -finline and -
Thanks for the patch and chasing down the magic.
Path is ok to commit.
--
steve
On Fri, Jul 19, 2024 at 05:32:26PM +0100, Paul Richard Thomas wrote:
> Hi All,
>
> Ping!
>
> I understand now why this works. The scope of the block is merged and so
> all the previous declarations that would othe
FYI,
For those that do not follow J3, their meeting just finished
this week. One noteworthy paper that passed was 24-166.txt,
"A modest proposal for adding an UNSIGNED type to Fortran".
The paper appears to have been author by Thomas (tkoening@).
Big "Thank You" to Thomas. I have wanted an unsi
On Fri, Jun 28, 2024 at 10:00:53PM +0200, Harald Anlauf wrote:
>
> the attached patch fixes an ICE occuring for ALLOCATE with SOURCE
> (or MOLD) of deferred character length in the scalar case, which
> looked obscure because the ICE disappears at -O1 and higher.
>
> The dump tree suggests that it
On Tue, Jun 18, 2024 at 09:13:23AM +0200, Gerald Pfeifer wrote:
> The original subsite has disappeared and we couldn't find it elsewhere.
>
https://github.com/gklimowicz/FCVS
gklimowicz is a flang developer and member of J3.
--
Steve
I don't know too much about the testsuite infrastructure.
You'll likely need to ping jakub or tobias, who seem to
be the most active gomp contributors.
On my FreeBSD system, I have my sources in gcc/gccx, build in
gcc/objx, and install into $HOME/work/x.
For building and testing, I have a script
Andre,
I have not seen an answer to your email. I just built gcc/gfortran with
a build directory named objx/. My 'make -j6 check-fortran' completed
without issues (other than the usual broken libsaniziter tests and
confusion of gmake versus make and $MAKE). From your description, it
would certa
On Thu, May 09, 2024 at 01:37:32PM +0800, Kewen.Lin wrote:
>
> >
> > That said, Fortran has the concept of model numbers, which
> > are set in arith.c. Does this change give the expected
> > value for ibm128? For example, with "REAL(16) X", one
> > has "DIGITS(X) = 113", which is the precision
On Wed, May 08, 2024 at 01:27:53PM +0800, Kewen.Lin wrote:
>
> Previously effective target fortran_real_c_float128 never
> passes on Power regardless of the default 128 long double
> is ibmlongdouble or ieeelongdouble. It's due to that TF
> mode is always used for kind 16 real, which has precisio
On Sat, Apr 06, 2024 at 05:54:43PM -0600, Neil Carlson wrote:
> What are the recommended options to use (e.g., --enable-libsanitize) when
> building GCC from source for the purpose of locating gfortran bugs? I'm
> trying to pin down a runtime memory corruption error, and I recall seeing
> at variou
On Wed, Mar 27, 2024 at 04:30:42PM +0100, Mikael Morin wrote:
> Hell(o),
>
> it didn't take long for my recent patch for PR111781 to show a regression.
> The fix proposed here is actually the one Harald posted in the PR.
> I can't imagine a case where it wouldn't do the right thing.
> Regression t
On Tue, Mar 19, 2024 at 04:17:32PM +0100, FX Coudert wrote:
>
> These two (independent) patches add two tiny Fortran 2023 features: new
> ISO_FORTRAN_ENV named constants and SELECTED_LOGICAL_KIND intrinsic.
>
> Bootstrapped and regtested on x86_64-pc-linux-gnu.
> Please review, and let me know i
On Wed, Mar 13, 2024 at 12:05:16PM +, Ken Woolridge wrote:
>
> When I attempt to link my test program (FF.F90) which calls UPPER_CASE (an
> assembly routine) I get the following error:
>
> C:/Program
> Files/GCC/bin/../lib/gcc/i686-pc-mingw32/13.2.0/../../../../i686-pc-mingw32/bin/ld.exe:
>
On Tue, Mar 05, 2024 at 08:06:10PM -0800, Jerry D wrote:
> On 3/5/24 1:51 PM, Harald Anlauf wrote:
> > Hi Jerry,
> >
> > on further thought, do we sanitize 'child_iomsg'?
> > We pass it to snprintf as format.
> >
> > Wouldn't a strncpy be sufficient?
> >
> > Harald
> >
> >
>
> Just to be safe
On Thu, Feb 29, 2024 at 10:28:19AM -0800, Jerry D wrote:
> On 2/29/24 10:13 AM, Steve Kargl wrote:
> > On Thu, Feb 29, 2024 at 09:36:43AM -0800, Jerry D wrote:
> > > On 2/29/24 1:47 AM, Bernhard Reutner-Fischer wrote:
> > >
> > > > And, just for my own educa
On Thu, Feb 29, 2024 at 09:36:43AM -0800, Jerry D wrote:
> On 2/29/24 1:47 AM, Bernhard Reutner-Fischer wrote:
>
> > And, just for my own education, the length limitation of iomsg to 255
> > chars is not backed by the standard AFAICS, right? It's just our
> > STRERR_MAXSZ?
>
> Yes, its what we ha
On Wed, Feb 28, 2024 at 10:42:36PM +, Ken Woolridge wrote:
> A little background: I have Intel's Fortran90 compiler which
> I used for years. However, I recently had to reinstall it
> and found that the key was no longer valid. Intel did not
> have the decency to return my emails so I looked
All,
Consider,
! { dg-do run }
program foo
implicit none
real y
associate (x => log(cmplx(-1,0)))
y = x%im
if (int(100*y)-314 /= 0) stop 1
end associate
end program
% gfcx -c a.f90
a.f90:6:13:
6 | y = x%im
| 1
Error: Symbol 'x' at (1) has no I
On Fri, Feb 23, 2024 at 10:15:17PM +0100, Harald Anlauf wrote:
> Hi Steve, all,
>
> here's an updated patch with an enhanced testcase that also
> checks MOLD= besides SOURCE=.
>
> Regtested on x86_64-pc-linux-gnu. Is it OK for mainline?
>
>From my viewpoint, yes.
Thanks for finding a better s
1 - 100 of 281 matches
Mail list logo
