Hi José, hi all,
especially since my patch which moved the descriptor conversion from
libgfortran to gfortran is in, I wonder whether there are still patches
to be applied and useful testcases; I assume there are more issues in
Bugzilla, especially as I filled myself some (often related to
polymo
Hi Tobias,
My disappearance is partly responsible for the backlog. I told José that I
would start working on it some months since but just have not had the time.
I can do some of the reviews but still do not have much time to spare.
Perhaps you could divide them up between us.
Andrew Benson has b
Hi José, hi Fortraners,
triage of all listed patches:
On 21.06.21 17:21, José Rui Faustino de Sousa wrote:
https://gcc.gnu.org/pipermail/fortran/2021-April/055924.html
PR100040 - Wrong code with intent out assumed-rank allocatable
PR100029 - ICE on subroutine call with allocatable polymorphi
Hi all,
On 22.10.21 15:05, Hafiz Abid Qadeer wrote:
This patch adds support for OpenMP 5.0 allocate clause for fortran. It does not
yet support the allocator-modifier as specified in OpenMP 5.1. The allocate
clause is already supported in C/C++.
I think the following shouldn't block the accept
On 10/18/2021 7:30 PM, Eric Gallager wrote:
On Tue, Oct 12, 2021 at 5:09 PM Eric Gallager wrote:
On Thu, Oct 6, 2016 at 10:41 AM Eric Gallager wrote:
Currently the build machinery handles install-pdf and install-html
targets, but no install-dvi target. This patch is a step towards
fixing t
I've committed this slightly cleaned-up version of the testcase
originally submitted with the now-fixed issue PR 94289.
-Sandra
commit c31d2d14f798dc7ca9cc078200d37113749ec3bd
Author: Sandra Loosemore
Date: Fri Oct 22 11:08:19 2021 -0700
Add testcase for PR fortran/94289
2021-10
Here's an obvious quick fix. Please apply.
diff --git a/gcc/fortran/decl.c b/gcc/fortran/decl.c
index 6043e100fbb..e889bb44142 100644
--- a/gcc/fortran/decl.c
+++ b/gcc/fortran/decl.c
@@ -5619,14 +5619,6 @@ match_attr_spec (void)
m = MATCH_ERROR;
goto cleanup;
Dear Fortranners,
the recently introduced shape validation for array components
in DT constructors did not properly deal with invalid code
created by ingenious testers.
Obvious solution: replace the gcc_assert by a suitable error message.
Regarding the error message: before the shape validation,
gfortran.dg/c-interop/cf-descriptor-5.f90 is associated with
5 FAILS on x86_64-*-freebsd.
Please fix.
--
Steve
libgomp.fortran/async_io_[1,2,3,4,8,9].f90 account for a number
of FAILS on x86_64-*-freebsd. Please fix.
--
Steve
Hi Steve,
Am 22.10.21 um 21:35 schrieb Steve Kargl via Fortran:
Here's an obvious quick fix. Please apply.
diff --git a/gcc/fortran/decl.c b/gcc/fortran/decl.c
index 6043e100fbb..e889bb44142 100644
--- a/gcc/fortran/decl.c
+++ b/gcc/fortran/decl.c
@@ -5619,14 +5619,6 @@ match_attr_spec (void)
On Fri, Oct 22, 2021 at 10:16:05PM +0200, Harald Anlauf wrote:
> Hi Steve,
>
> Am 22.10.21 um 21:35 schrieb Steve Kargl via Fortran:
> > Here's an obvious quick fix. Please apply.
> >
> >
> > diff --git a/gcc/fortran/decl.c b/gcc/fortran/decl.c
> > index 6043e100fbb..e889bb44142 100644
> > ---
Hi Tobias,
Am 22.10.21 um 15:06 schrieb Tobias Burnus:
https://gcc.gnu.org/pipermail/fortran/2021-April/055934.html
PR100103 - Automatic reallocation fails inside select rank
Still segfaults at runtime for 'that = a' where the RHS is a parameter
and the LHS an allocatable assumed-rank array (
Hi Tobias, José,
Am 22.10.21 um 15:06 schrieb Tobias Burnus:
https://gcc.gnu.org/pipermail/fortran/2021-April/055949.html
PR100136 - ICE, regression, using flag -fcheck=pointer
First testcase has an ICE with -fcheck=pointer
Second testcase has always an ICE + possibly missing func.
TODO: Re
Hi Tobias, José,
Am 22.10.21 um 15:06 schrieb Tobias Burnus:
https://gcc.gnu.org/pipermail/fortran/2021-April/055982.html
PR100245 - ICE on automatic reallocation.
Still ICEs
TODO: Review patch.
this one works and LGTM.
Thanks for the patch!
Harald
The testcase of the PR or as attached gave an ICE, but only when
compiled with -fcheck=all -fsanitize=undefined. Solution: Strip
the nop to avoid the assert failure.
Committed as r12-4632-g24e99e6ec1cc57f3660c00ff677c7feb16aa94d2
Tobias
* * *
PS: Similar issues when using additional flags:
I
Committed as r12-4633-g030875c197e339542ddfcbad90cfc01263151bec
To reduce the XFAIL clutter in the *.sum files, this patch removes some
pointless XFAIL in favour of pruning the output which should be ignored
and using explicit checks for the currently output warnings/errors.
Tobias
-
On Fri, Oct 22, 2021 at 8:23 AM Jeff Law wrote:
>
>
>
> On 10/18/2021 7:30 PM, Eric Gallager wrote:
> > On Tue, Oct 12, 2021 at 5:09 PM Eric Gallager wrote:
> >> On Thu, Oct 6, 2016 at 10:41 AM Eric Gallager wrote:
> >>> Currently the build machinery handles install-pdf and install-html
> >>> ta
I've committed another testcase from a bugzilla issue that now appears
to be fixed.
-Sandra
commit 9a0e34eb45e36d4f90cedb61191fd31da0bab256
Author: Sandra Loosemore
Date: Fri Oct 22 17:22:00 2021 -0700
Add testcase for PR fortran/95196
2021-10-22 José Rui Faustino de Sousa
Hello All,
I am working on a custom float in RISC-V 32, one can replace keyword
"float" with custom keyword like "fp_custom" at line # 482
riscv-gcc/gcc/c-family/c-common.c. But in the case of Fortran, can you
please tell which files to modify to replace the "float" keyword?
And also, in case o
20 matches
Mail list logo