Hi Yuao,
Yuao Ma wrote:
Following up on your review comments, I have updated the patch.
Thanks - LGTM.
Two minor comments, but I have already pushed the commit
as r16-602-gb239e9cf98ca92
First:
* gfortran.dg/dec_math.f90: Add atand(y, x) testcase.
Also for the documentation, the
Admittedly, this *PING* is rather early – but as more trigonometric
functions changes are coming, I think it would be useful to agree
that this is a good approach.
And the patch is simple.
BTW: For the infrastructure/download update,
I have filed https://gcc.gnu.org/PR120237
Next would be the s
Hi Jakub,
Jakub Jelinek wrote:
As mentioned in the PR, _gfortran_{,m,s}findloc2_s{1,4} iterate too many
times in the back case if nothing is found.
For !back, the loops are for (i = 1; i <= extent; i++) so i is in the
body [1, extent] if nothing is found, but for back it is
for (i = extent; i >
Jakub Jelinek wrote:
There is a bug in _gfortran_s{max,min}loc1_{4,8,16}_s{1,4} which the
following testcase shows.
The functions return but then crash in the caller.
Seems that is because buffer overflows, I believe those functions for
if (mask == NULL || *mask) condition being false are sup
First is slightly confusing as there are three patches for PR120191.
In particular, two which look almost identical - one for loc2 (this one)
and one for loc1 (the one sent one our later). Jakub pointed out that
the remarks after "ok for trunk?" for this patch are obsoleted by
the follow up patch
Jakub Jelinek wrote:
Here is an updated patch including your incremental changes.
Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
LGTM. Thanks for the patch – and sorry for the delayed review.
Tobias
Trying to write a testcase I've run into further issues but seems they
Hi!
As mentioned in the PR, _gfortran_{,m,s}findloc2_s{1,4} iterate too many
times in the back case if nothing is found.
For !back, the loops are for (i = 1; i <= extent; i++) so i is in the
body [1, extent] if nothing is found, but for back it is
for (i = extent; i >= 0; i--) so i is in the body
Hello world,
the attached patch fixes a 15/16 regression and should be fairly
self-explanatory.
Regarding testing: I'm not sure I am up to the task of hacking
dejagnu to do this. I am now running local tests, which is
better than nothing (I guess).
Regression-testing: Passed, though this does n
Hello world,
this fixes the other regression which crept in with gfortran.
Again, regression-tested, plus the local testing script is
attached.
Ok for trunk and gcc-15?
Best regards
Thomas
Fix explicit arrays with non-constant size for -fc-prototypes.
gcc/fortran/ChangeLog:
Hi Tobias,
> Admittedly, this *PING* is rather early – but as more trigonometric
> functions changes are coming, I think it would be useful to agree
> that this is a good approach.
Patch is OK to push.
FX
Hi Thomas,
Same remark as for PR120107! LGTM for both branches.
Thanks
Paul
On Tue, 13 May 2025 at 21:30, Thomas Koenig wrote:
> Hello world,
>
> this fixes the other regression which crept in with gfortran.
> Again, regression-tested, plus the local testing script is
> attached.
>
> Ok for
Hi Thomas,
I don't think that anybody else has been up to the job of hacking dejagnu
to test patches to dump-parse-tree.cc :-)
I think that the patch verges on the 'obvious' and is good for both
15-branch and mainline.
Thanks for the patch.
Paul
On Tue, 13 May 2025 at 21:15, Thomas Koenig wr
12 matches
Mail list logo