On 10/11/23 12:39 PM, Harald Anlauf wrote:
Dear All,
the attached trivial patch fixes (= catches) a forgotten corner-case
in the detection of a name conflict between an internal procedure and
a local declaration for the case that the latter is a derived type.
Another torture test by Gerhard... ;
On 10/11/23 12:44 PM, Harald Anlauf wrote:
Dear All,
sorry for attaching the wrong patch - this time it is the correct one!
Harald
On 10/11/23 21:39, Harald Anlauf wrote:
Dear All,
the attached trivial patch fixes (= catches) a forgotten corner-case
in the detection of a name conflict betwee
On 10/16/23 12:11 PM, Harald Anlauf wrote:
Dear All,
the attached patch fixes a dependency check in frontend optimzation
for nested implied-do IO. The problem appeared for >= 3 loops only
as the check considered dependencies to be only of band form instead
of triangular form.
Regtested on x86_
On 2/29/24 12:56 PM, Harald Anlauf wrote:
Dear all,
here's a first patch addressing issues with NULL as actual argument:
if the dummy is assumed-rank or assumed length, MOLD shall be present.
There is also an interp on interoperability of c_sizeof and NULL
pointers, for which we have a partiall
On 3/1/24 11:24 AM, rep.dot@gmail.com wrote:
Hi Jerry and Steve,
On 29 February 2024 19:28:19 CET, 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
EN, child_iomsg)
+ 1;
free_line (dtp);
snprintf (message, child_iomsg_len, child_iomsg);
generate_error (&dtp->common, dtp->u.p.child_saved_iostat,
plus several more. Wouldn't it be better to increase the size of
message by one?
Thanks,
Harald
On 3/5/24
On 3/6/24 9:13 AM, Harald Anlauf wrote:
Hi Jerry,
can you please replace the user message in e.g. your new testcase
pr105456-wf.f90 by say:
piomsg="The users message containing % and %% and %s and other stuff"
This behaves as expected with Intel, but dies horribly with gfortran
after your patc
Hi all,
There has been a bit of discussio on which way to go on this.
I took a look today and this trivial patch gives the behavior concluded
on Fortran Discourse. See the bugzilla for all the relevant information.
Regresion tested on x86-64.
I will do the appropriate changelog.
OK for trun
On 3/27/24 1:42 PM, Harald Anlauf wrote:
Dear all,
the attached patch fixes a 10+ regression for cases where a
derived type with a pointer component is used in a DATA statement.
The failure looked obscure, see testcase comments, and pointed
to a possible issue in the resolution (order). For the
Hi all,
The attached log entry and patch (git show) fixes this issue by adding
logic to handle spaces in eat_separators. One or more spaces by
themselves are a valid separator. So in this case we look at the
character following the spaces to see if it is a comma or semicolon.
If so, I change
On 4/4/24 2:31 AM, Tobias Burnus wrote:
Hi Jerry,
Jerry D wrote:
The attached log entry and patch (git show) fixes this issue by adding
logic to handle spaces in eat_separators. One or more spaces by
themselves are a valid separator. So in this case we look at the
character following the
On 4/4/24 2:31 AM, Tobias Burnus wrote:
Hi Jerry,
--- snip ---
The patch looks mostly like I would expect, except for decimal='point'
and a ';' which is *not* preceded by a space.
Thanks for working on it.
Regarding the 'except' case:
--- snip ---
i.e. for the following string, I had *ex
On 4/4/24 2:41 PM, Tobias Burnus wrote:
Hi Jerry,
I think for the current testcases, I like the patch – the question is
only what's about:
',3' as input for 'comma' (or '.3' as input for 'point')
For 'point' – 0.3 is read and ios = 0 (as expected)
But for 'comma':
* GCC 12 reads nothing
On 4/5/24 10:47 AM, Jerry D wrote:
On 4/4/24 2:41 PM, Tobias Burnus wrote:
Hi Jerry,
I think for the current testcases, I like the patch – the question is
only what's about:
',3' as input for 'comma' (or '.3' as input for 'point')
For &
On 4/8/24 2:53 AM, Tobias Burnus wrote:
Jerry D wrote:
See attached updated patch.
It turned rather quickly out that this patch – committed as
r14-9822-g93adf88cc6744a – caused regressions.
Namely, real-world code use tab(s) as separator instead of spaces.
[For instance, PR114304 which
On 4/8/24 2:45 AM, Paul Richard Thomas wrote:
Hi All,
This one is blazingly 'obvious'. I haven't had the heart to investigate why somebody thought that it is a good idea to check if unreferenced symbols are finalizable because, I suspect, that
'somebody' was me. Worse, I tried a couple of other
On 1/30/24 12:36 PM, Harald Anlauf wrote:
Hi Jerry,
Am 30.01.24 um 19:15 schrieb Jerry D:
The attached patch attempts to fix the handling of the EN0.0E0 and
ES0.0E0 formatting by correctly calculating the number of digits needed
for the exponents and building those exponents into the float
On 2/8/24 1:03 PM, Harald Anlauf wrote:
Dear all,
the attached patch improves error recovery when we encounter an
array constructor where a unary operator (e.g. minus) is applied
and -frange-check is active. The solution is not to terminate
early in that case to avoid inconsistencies between ch
The attached patch fixes this PR by properly adjusting some variables
When using stream io. See log below. New test case included.
Regression tested on x86_64.
OK for trunk and backport?
Regards,
Jerry
ChangeLog:
libgfortran: Adjust bytes_left and pos for access="STREAM".
During tab
Pushed as simple and obvious.
Regards,
Jerry
commit 8221201cc59870579b9dc451b173f94b8d8b0993 (HEAD -> master,
origin/master, origin/HEAD)
Author: Steve Kargl
Date: Wed Feb 14 14:40:16 2024 -0800
Fortran: namelist-object-name renaming.
PR fortran/105847
gcc/fortran/Ch
On 2/16/24 1:40 PM, Harald Anlauf wrote:
Dear all,
this patch fixes a regression which was a side-effect of r14-8947,
losing the length of a deferred-length character variable when
passed as a dummy.
The new testcase provides a workout for deferred length to improve
coverage in the testsuite.
The attached patch fixes this one. Se the ChangeLog below for explanation.
OK for trunk?
I think simple enough to backport to 13 as well.
Regards,
Jerry
Author: Jerry DeLisle
Date: Fri Feb 16 17:06:37 2024 -0800
libgfortran: Fix namelist read.
PR libgfortran/107068
l
Hello,
I posted the attached patch in bugzilla some time ago. This includes a
new test case. The patch adds additional checks in key places to catch
eroneous use of semicolons
Regression tested on x86_64,
OK for trunk and later backport to 13?
Jerrydiff --git a/gcc/testsuite/gfortran.dg/pr1
On 2/21/24 10:30 AM, Steve Kargl wrote:
I have attached a patch to PR114024, see
https://gcc.gnu.org/pipermail/gcc-bugs/2024-February/854651.html
The patch contains a new testcase and passes regression
testing on x86_64-*-freebsd. Could someone castr an eye
over the patch and commit it?
Hi
On 2/21/24 12:28 PM, Harald Anlauf wrote:
On 2/21/24 20:41, Jerry D wrote:
On 2/21/24 10:30 AM, Steve Kargl wrote:
I have attached a patch to PR114024, see
https://gcc.gnu.org/pipermail/gcc-bugs/2024-February/854651.html
The patch contains a new testcase and passes regression
testing on
Hi all,
The attached fix adds a check for an error condition from a UDDTIO
procedure in the case where there is no actual underlying error, but the
user defines an error by setting the iostat variable manually before
returning to the parent READ.
I did not address the case of a formatted WRI
On 2/25/24 12:34 PM, Harald Anlauf wrote:
Hi Jerry,
On 2/22/24 20:11, Jerry D wrote:
Hi all,
The attached fix adds a check for an error condition from a UDDTIO
procedure in the case where there is no actual underlying error, but the
user defines an error by setting the iostat variable
On 2/25/24 12:26 PM, Harald Anlauf wrote:
Dear all,
the attached simple patch fixes an issue where we evaluated
polymorphic functions twice in assignments: once for the _data
component, and once for the _vptr. Using save_expr prevents
the double evaluation.
Regtested on x86_64-pc-linux-gnu. O
On 2/27/24 1:00 PM, Harald Anlauf wrote:
Dear all,
the attached patch fixes invalid Fortran in testcase
gfortran.dg/pr101026.f, which might prohibit progress
in fixing pr111781. (Note that the testcase was for a
tree-optimizer issue, not the Fortran frontend.)
OK for mainline?
Will commit wit
The attached patch adds the error checks similar to the first patch
previously committed.
I noticed a redundancy in some defines MSGLEN and IOMSG_LEN so I
consolidated this to one define in io.h. This is just cleanup stuff.
I have added test cases for each of the places where UDTIO is done in
On 2/29/24 1:47 AM, Bernhard Reutner-Fischer wrote:
On Wed, 28 Feb 2024 21:29:06 -0800
Jerry D wrote:
The attached patch adds the error checks similar to the first patch
previously committed.
I noticed a redundancy in some defines MSGLEN and IOMSG_LEN so I
consolidated this to one define in
On 1/20/24 10:46 AM, Alexander Westbrooks wrote:
Hello and Happy New Year!
I wanted to follow up on this patch I made to address PR82943 for
GFortran. Has anyone had a chance to review it?
Thanks,
Alexander Westbrooks
Inserting myself in here just a little bit. I will apply and test toda
On 1/20/24 11:08 AM, Jerry D wrote:
On 1/20/24 10:46 AM, Alexander Westbrooks wrote:
Hello and Happy New Year!
I wanted to follow up on this patch I made to address PR82943 for
GFortran. Has anyone had a chance to review it?
Thanks,
Alexander Westbrooks
Inserting myself in here just a
On 1/20/24 12:08 PM, Harald Anlauf wrote:
Am 20.01.24 um 20:08 schrieb Jerry D:
On 1/20/24 10:46 AM, Alexander Westbrooks wrote:
Hello and Happy New Year!
I wanted to follow up on this patch I made to address PR82943 for
GFortran. Has anyone had a chance to review it?
Thanks,
Alexander
The attached patch attempts to fix the handling of the EN0.0E0 and
ES0.0E0 formatting by correctly calculating the number of digits needed
for the exponents and building those exponents into the float string.
My editor judiciously deleted trailing blank spaces in a number of
places. I apologi
The following has been committed per discussion in the subject PR.
commit 95b70545331764c85079a1d0e1e19b605bda1456 (HEAD -> master,
origin/master, origin/HEAD)
Author: Jerry DeLisle
Date: Wed Dec 13 19:04:50 2023 -0800
fortran: Add degree based trig functions for F2023
PR f
Committed as simple and obvious. Initial patch thanks to Steve.
When using git gcc-commit-mklog how does one add in the coauthor?
The master branch has been updated by Jerry DeLisle :
https://gcc.gnu.org/g:add995ec117d756e61d207041cd32f937c1a1cd9
commit r14-6986-gadd995ec117d756e61d207041cd32f
On 12/6/23 8:09 AM, Paul Richard Thomas wrote:
Dear All,
This patch was rescued from my ill-fated and long winded attempt to
provide a fix-up for function selector references, where the function is
parsed after the procedure containing the associate/select type
construct (PRs 89645 and 99065)
On 6/3/24 1:12 PM, Harald Anlauf wrote:
Dear all,
the attached simple patch fixes an ICE for ALLOCATE with SOURCE=
of a deferred-length character array with source-expression
being an array of character with length zero. The reason was
that the array descriptor of the source-expression was disc
On 8/19/24 4:43 AM, Andre Vehreschild wrote:
Hi all,
another ping on this patch.
Regtests ok on x86_64-pc-linux-gnu on updated master. Ok for mainline?
Regards,
Andre
Looks OK to go ahead Andre.
Thanks,
Jerry
On Fri, 9 Aug 2024 16:29:08 +0200
Andre Vehreschild wrote:
Ping!
O
On 8/20/24 5:35 AM, Andre Vehreschild wrote:
Hi all,
pinging this patch.
Regtests ok on x86_64-pc-linux-gnu / Fedora 39. Ok for mainline?
Regards,
Andre
Your approach looks reasonable so I think OK to push.
Thanks,
Jerry
On 6/18/24 10:20 AM, Steve Kargl wrote:
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.
FWIW my copy of the tests st
Hi all,
The attached patch fixes this by avoiding looking for and avoiding the
EOF condition in the parent READ after returning from the child IO process.
I could not think of a simple test case yet since the problem occurred
only when redirecting the input to the test program via a pipe. If
On 7/22/24 8:13 AM, Jerry D wrote:
Hi all,
The attached patch fixes this by avoiding looking for and avoiding the
EOF condition in the parent READ after returning from the child IO process.
I could not think of a simple test case yet since the problem occurred
only when redirecting the
I plan to push this soon to hopefully fix some test breakage on some
architetures. It is simple and obvious. I did not get any feedback on
this and I do not have access to the machines in question.
Regression tested on linux-x86-64.
Regards,
Jerry
commit bc4ee05dc7c60d534ef927ac5e679f67fb99
Hi all,
Doing some catchup here. I plan to commit the following shortly. This is
one of Steve's patches posted on bugzilla.
I have created a new test case.
Regression tested on linux x86-64.
git show:
commit 4d4549937b789afe4037c2f8f80dfc2285504a1e (HEAD -> master)
Author: Steve Kargl
Date
Hi all,
The attached patch changes all the snprintf calls to regular gfc_error
calls to cleanup translation. I introduced a simple macro to facilitate
doing the checks that were being done in the bad_op code section.
From the description for the call to gfc_extend_expr interfaces are
mentio
On 9/5/24 12:42 PM, Harald Anlauf wrote:
Dear all,
the attached simple patch fixes a corner case related to pr84868,
which was tracked separately. While Paul's patch for pr84868 added
the framework for treating len_trim in the specification part of
a character function, it missed the possibilit
On 10/12/24 9:04 AM, Thomas Koenig wrote:
Hello world,
the attached patch implements the constants for UNSIGNED for
ISO_FORTRAN_ENV and ISO_C_BINDING. With this, the implementation
of UNSIGNED for gfortran should be complete, modulo bugs, of course.
OK for trunk?
Looks good to go Thomas.
Th
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
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
The attached diff file begins some test suite cleanup.
The patch removes extra spaces between dg-do and the run directive, I
only have gone through gfortran.dg and not its sub-directories.
Interestingly, one of the tests fails when this space is removed. I
fixed that by adding in a -O in the d
On 10/20/24 1:16 PM, Harald Anlauf wrote:
Hi Jerry!
Am 20.10.24 um 21:53 schrieb Jerry D:
On 10/20/24 12:23 PM, Harald Anlauf wrote:
Hi Jerry!
Am 20.10.24 um 18:56 schrieb Jerry D:
The attached diff file begins some test suite cleanup.
The patch removes extra spaces between dg-do and the
On 10/20/24 12:23 PM, Harald Anlauf wrote:
Hi Jerry!
Am 20.10.24 um 18:56 schrieb Jerry D:
The attached diff file begins some test suite cleanup.
The patch removes extra spaces between dg-do and the run directive, I
only have gone through gfortran.dg and not its sub-directories
Pushed as stated in the PR to cleanup the test case.
commit 6604a05fa27bc21c3409e767552daca3fcf43964 (HEAD -> master,
origin/master, origin/HEAD)
Author: Jerry DeLisle
Date: Thu Oct 17 13:39:09 2024 -0700
Fortran: Add tolerance to real value comparisons.
gcc/testsuite/ChangeLog:
On 10/17/24 12:52 PM, Thomas Koenig wrote:
Hello world,
The attached patch fixes an ICE when an UNSIGNED-specific constant
is used from ISO_FORTRAN_ENV. The error message is not particularly
great, it is
Error: Unsigned: The symbol 'uint32', referenced at (1), is not in the
selected standard
On 10/29/24 2:00 PM, Harald Anlauf wrote:
Dear all,
while looking at the recent testcase gfortran.dg/pr115070.f90 with f951
running under valgrind, I noticed minor front-end memleaks of gfc_expr's
that are probably fallout from a code refactoring, which are fixed by
the attached.
Regtested on x
On 10/30/24 9:58 AM, Steve Kargl wrote:
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. Th
On 11/2/24 8:44 AM, Thomas Koenig wrote:
Ping **(5./7.) ?
MASKR and MASKL are obvious candidates for unsigned, too; in the
previous version of the doc patch, I had promised that these would
take unsigned arguments in the future. What I had in mind was
they could take an unsigned argument and re
On 11/12/24 5:23 AM, Paul Richard Thomas wrote:
Hi All,
The ChangeLog and comment make it clear what this patch does and why.
OK for mainline and backporting after a week or so?
Regards
Paul
In the test case:
A comment s/resul/result/
Also the test conditional
if (trim (array_strings2(i
On 9/23/24 11:21 PM, Hans-Peter Nilsson wrote:
Here's a general approach to handle PR116701. I considered
adding manual deletions as quoted below and mentioned in the
PR, but seeing the handling of "integer 8" in
fortran-torture-execute I decided to follow that example:
better scan the source fo
On 9/18/24 1:20 PM, Thomas Koenig wrote:
OK for trunk?
OK and thanks.
Jerry
--- snip ---
On 9/24/24 5:46 PM, Hans-Peter Nilsson wrote:
Thanks for the review!
Date: Tue, 24 Sep 2024 17:10:27 -0700
Cc: Jerry D
From: Jerry D
On 9/23/24 11:21 PM, Hans-Peter Nilsson wrote:
I hope the inclusion of gfortran-dg.exp in
fortran-torture.exp is not controversial, but there's no
fo
I would like to commit the attached patch for Steve.
Regression tested on x86-64-linux-gnu.
OK for trunk?
Author: Steve Kargl
Date: Sun Nov 24 18:26:03 2024 -0800
Fortran: Check IMPURE in BLOCK inside DO CONCURRENT.
PR fortran/117765
gcc/fortran/ChangeLog:
On 11/25/24 3:09 AM, Paul Richard Thomas wrote:
Hi All,
The breakage was caused by the patch for PR109345. As it happens, this
part of the patch was not required to fix the PR and looked to be a
considerable simplification of the condition. Although correct that all
is left are class dummies,
On 11/27/24 12:31 PM, Harald Anlauf wrote:
Dear all,
the attached patch fixes a wrong-code issue with bounds-checking
enabled when doing I/O of an array section and an index is either
an expression or a function result. The problem does not occur
without bounds-checking.
When looking at the or
On 11/20/24 1:08 PM, Harald Anlauf wrote:
Dear all,
the attached, actually rather straightforward patch fixes the checking of
protected variables in submodules. When a variable was use-associated
in an ancestor module, we failed to properly diagnose this.
Regtested on x86_64-pc-linux-gnu. OK
On 11/13/24 2:26 PM, Harald Anlauf wrote:
Dear all,
the attached patch is the third part of a series to fix the handling of
NULL() passed to pointer dummy arguments. This one addresses character
dummy arguments (scalar, assumed-shape, assumed-rank) for various
uses in the caller.
The patch is
On 11/17/24 2:21 PM, Harald Anlauf wrote:
Dear all,
the attached patch fixes a rejects-valid / rejects-potentially-valid code issue
for ALLOCATE of CHARACTER with type-spec, and add character length checking
with -fcheck=bounds for the case at hand. It also improves checking of
character funct
Suggested docs change regarding fix to PR88052.
See attached diff file.
OK to push?
Regards,
Jerry
diff --git a/htdocs/gcc-15/changes.html b/htdocs/gcc-15/changes.html
index 46dad391..2dc222e3 100644
--- a/htdocs/gcc-15/changes.html
+++ b/htdocs/gcc-15/changes.html
@@ -143,6 +143,10 @@ a work-
On 11/23/24 10:59 AM, Harald Anlauf wrote:
Am 23.11.24 um 19:35 schrieb Jerry D:
Suggested docs change regarding fix to PR88052.
See attached diff file.
OK to push?
Regards,
Jerry
Jerry,
for clarification: isn't it the language standard option used when
compiling the main th
Hi all,
Attached patch adds a test for zero that is needed for write_boz to work
correctly. Almost obvious.
Regression tested on x86_64.
Ok for trunk?
Jerry
Author: Jerry DeLisle
Date: Mon Dec 2 19:45:26 2024 -0800
Fortran: Fix B64.0 formatted write output.
PR fortran/1
On 9/23/24 1:00 AM, Andre Vehreschild wrote:
Hi Anuj,
please check the code style of your patch using:
contrib/check_GNU_style.py
It reports several errors with line length and formatting.
I am going to work with Tobias to move this along. I have the style
things fixed. I am going to work
On 1/6/25 2:06 AM, Andre Vehreschild wrote:
Hi all,
pinging attached rebased patch.
Regtests ok on x86_64-pc-linux-gnu / F41. Ok for mainline?
- Andre
On Thu, 12 Dec 2024 14:50:13 +0100
Andre Vehreschild wrote:
Hi all,
attached patch improves analysis of cycles in derived types, i.e. type
On 1/6/25 6:21 AM, Andre Vehreschild wrote:
Hi all,
during looking for something completely different, I figured, that gcc does not
use std::set internally, but its implementation of hash_set. I therefore
adapted the patch to use it. Nothing more changed.
Still regtests ok on x86_64-pc-linux-gn
On 1/6/25 2:08 AM, Andre Vehreschild wrote:
Hi all,
attached patch has been rebased to latest trunk. Just pinging!
Regtests ok on x86_64-pc-linux-gnu / F41. Ok for mainline?
- Andre
On Fri, 13 Dec 2024 12:10:58 +0100
Andre Vehreschild wrote:
Hi all,
attached patch fixes deep-copying (or r
Attached is the revised patch incorporating handling of optional
arguments of a calling procedure and simplified checking for C
interoperability.
See the PR for much discussion.
Regression tested on x86_64_linux_gnu.
Two test cases.
OK for trunk?
Author: Steven G. Kargl
Date: Sun Dec 29
n.
commit efc0981077a70c4de4596f682c4aeade07ec2f17 (HEAD -> master,
origin/master, origin/HEAD)
Author: Steven G. Kargl
Date: Sun Dec 29 14:19:18 2024 -0800
Fortran: Implement f_c_string function.
On Sun, 29 Dec 2024 at 23:10, Jerry D <mailto:jvdelis...@gmail.com>> wrote:
Attached is the revis
On 2/3/25 11:55 AM, Thomas Koenig wrote:
Hello world,
with the following patch to the failing test case
diff --git a/gcc/testsuite/gfortran.dg/unsigned_15.f90 b/gcc/testsuite/
gfortran.dg/unsigned_15.f90
index da4ccd2dc17..80a7a54e380 100644
--- a/gcc/testsuite/gfortran.dg/unsigned_15.f90
+++
On 2/3/25 2:14 PM, Vincent Vanlaer wrote:
Hi all,
Gentle ping for the patch below: https://gcc.gnu.org/pipermail/
fortran/2024-December/061467.html
Best wishes,
Vincent
On 30/12/2024 00:19, Vincent Vanlaer wrote:
The -MT and -MQ options should replace the default target in the
generated dep
On 2/3/25 2:49 AM, Richard Sandiford wrote:
Steve Kargl writes:
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
On 1/29/25 10:30 AM, Jerry D wrote:
Follow-up:
On 1/28/25 1:33 PM, Harald Anlauf wrote:
Jerry,
while I haven't read your actual patch yet, I think the testcase
is slightly incorrect. In fact, Intel, NAG, Nvidia and AMD flang
disagree with it.
--- snip ---
The following adjustment t
Committed as:
commit e41a5a2a0832509fa1c0b7cab0c8001fadbd23d4 (HEAD -> master,
origin/master, origin/HEAD)
Author: Jerry DeLisle
Date: Tue Feb 4 17:21:42 2025 -0800
Fortran: Fix PR 47485.
The -MT and -MQ options should replace the default target in the
generated dependency file
On 1/30/25 1:44 PM, Harald Anlauf wrote:
Dear all,
analyzing the the PR (by Gerhard) turned out to two slightly related
issues. The first one, where a variable in a COMMON block is falsely
resolved to a derived type declared in the host, leads to a false
freeing of the symbol, resulting in memo
On 2/4/25 9:29 AM, Jerry D wrote:
On 2/3/25 4:46 PM, Vincent Vanlaer wrote:
On 4/02/2025 01:42, Jerry D wrote:
On 2/3/25 2:14 PM, Vincent Vanlaer wrote:
Hi all,
Gentle ping for the patch below: https://gcc.gnu.org/pipermail/
fortran/2024-December/061467.html
Best wishes,
Vincent
On 30
On 2/3/25 4:46 PM, Vincent Vanlaer wrote:
On 4/02/2025 01:42, Jerry D wrote:
On 2/3/25 2:14 PM, Vincent Vanlaer wrote:
Hi all,
Gentle ping for the patch below: https://gcc.gnu.org/pipermail/
fortran/2024-December/061467.html
Best wishes,
Vincent
On 30/12/2024 00:19, Vincent Vanlaer
On 1/31/25 11:30 AM, Harald Anlauf wrote:
--- snip --
So either commit the current version and track this issue in
a PR if not yet done, or have a look if there is a quick fix.
Thanks for the work!
Harald
Committed as:
commit cfed99751c1a3b93ca66451eb1b62271e682f927 (HEAD -> master,
origin/
On 1/31/25 11:30 AM, Harald Anlauf wrote:
Hi Jerry,
Am 30.01.25 um 21:50 schrieb Jerry D:
On 1/29/25 10:30 AM, Jerry D wrote:
Follow-up:
On 1/28/25 1:33 PM, Harald Anlauf wrote:
Jerry,
while I haven't read your actual patch yet, I think the testcase
is slightly incorrect. In fact,
On 2/1/25 10:25 AM, Harald Anlauf wrote:
Dear all,
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
conformance is requested.
Re
On 1/31/25 11:30 AM, Harald Anlauf wrote:
Hi Jerry,
Am 30.01.25 um 21:50 schrieb Jerry D:
On 1/29/25 10:30 AM, Jerry D wrote:
Follow-up:
On 1/28/25 1:33 PM, Harald Anlauf wrote:
Jerry,
while I haven't read your actual patch yet, I think the testcase
is slightly incorrect. In fact,
Pushed r15-6090-gcf406a6c
Thanks for the review!
Jerry
On 12/10/24 12:15 AM, Andre Vehreschild wrote:
Hi Jerry,
patch looks good. Ok for mainline and backport after grace period.
Thanks for the patch,
Andre
On Mon, 9 Dec 2024 20:31:08 -0800
Jerry D wrote:
Hi all,
The attached
Hi all,
The attached patch fixes this bug by checking for the case of a short
READ that should be padded with blanks and if the BZ mode is enabled,
those blanks should be treated as trailing zero's.
New test case courtesy Malcom Cohen.
Regression tested on X86_64_linux_gnu.
OK for trunk and
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 crashes here with a segfault:
program foo
use iso_c_binding, only : c_null_char
Andre, have you tested this with the tests in OpenCoarrays suite?
I ask since this touches coarray things.
Jerry
On 12/16/24 1:58 AM, Andre Vehreschild wrote:
PING!
On Fri, 6 Dec 2024 19:10:08 +0100
Andre Vehreschild wrote:
Hi all,
I had to dive deeply into the issue with handling allocat
On 12/19/24 1:34 PM, Harald Anlauf wrote:
Dear all,
the check for potential aliasing of lhs and rhs currently shortcuts
if the types differ. This is a problem if one is of type complex
and the other is of type real (and of the same kind parameter value),
as this ignores that F2008 inquiry refer
On 12/19/24 4:13 AM, Andre Vehreschild wrote:
Hi all,
attached patch fixes a rather old open issue, that I stumbled upon
while trying to figure, why a test failed on the command line but not
in the testsuite. The implementation of the STOP command in caf_single
did not hand the errorcode over to
Hi all,
I had originally created this patch in 2018 and we did not get back to
it. This results in more restrictive runtime behavior. I will go through
the front-end code with another patch to catch this at compile time.
Changelog and new test case. See attached patch.
OK for trunk
Author:
On 11/23/24 12:40 AM, Thomas Koenig wrote:
Hi Jerry,
I had originally created this patch in 2018 and we did not get back to
it. This results in more restrictive runtime behavior. I will go
through the front-end code with another patch to catch this at compile
time.
Changelog and new test ca
On 12/20/24 9:09 AM, Andre Vehreschild wrote:
Thank you very much Jerry.
The delta between the two patches is really minor. In resolve.c I have
removed some attr.pointer setting and in caf/single.c the handling for
those as well as treating non-descriptor arrays differently.
Most changes in
On 1/7/25 12:06 PM, Jerry D wrote:
On 9/25/24 3:18 AM, Andre Vehreschild wrote:
Hi all,
I finally managed to apply the fixed patch. It still had some stray
line break
so check_GNU_style.py wouldn't succeed. But with that fixed I agree to
have
only some nonsense bickering of the script
1 - 100 of 180 matches
Mail list logo
