https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98445
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |INVALID
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98454
--- Comment #5 from anlauf at gcc dot gnu.org ---
(In reply to kargl from comment #4)
> Should be closed as invalid as the original code contains a number
> of issues caused by invalid code.
Steve, stop it!
My reduced testcase shows that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98454
--- Comment #10 from anlauf at gcc dot gnu.org ---
(In reply to martin from comment #9)
> Problems with default initialisation of function result were fixed with
> PR45489. The relevant testcase added by this PR is initialization_27.f90
&
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98458
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
CC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98454
--- Comment #11 from anlauf at gcc dot gnu.org ---
The following hack fixes the testcase in comment#10,
but not the testcase in comment#2:
diff --git a/gcc/fortran/resolve.c b/gcc/fortran/resolve.c
index 249f402b8d9..2c9570d4641 100644
--- a/gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93685
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96418
--- Comment #6 from anlauf at gcc dot gnu.org ---
(In reply to Andre Vehreschild from comment #5)
> Patch submitted as:
> https://gcc.gnu.org/pipermail/fortran/2020-August/054943.html
> Waiting for review.
Hi Andre,
any progress her
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96381
--- Comment #2 from anlauf at gcc dot gnu.org ---
The following patch fixes the invalid read:
diff --git a/gcc/fortran/class.c b/gcc/fortran/class.c
index 5677d920239..783e4c7354b 100644
--- a/gcc/fortran/class.c
+++ b/gcc/fortran/class.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93794
--- Comment #5 from anlauf at gcc dot gnu.org ---
> Paul,
>
> are you still working on this?
Paul,
this is still one of yours...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96381
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93794
--- Comment #7 from anlauf at gcc dot gnu.org ---
(In reply to Paul Thomas from comment #6)
> Hah! I am probably a week or two from getting to it. I have been working my
> way through a backlog but have been held up for some days by unl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96986
--- Comment #2 from anlauf at gcc dot gnu.org ---
F2018 has:
! 15.4.2.2 Explicit interface
! Within the scope of a procedure identifier, the procedure shall have an
! explicit interface if it is not a statement function and
! (3) the procedure
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98263
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96381
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||dcb314 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89891
Bug 89891 depends on bug 98263, which changed state.
Bug 98263 Summary: valgrind error in gfc_find_derived_vtab
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98263
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96986
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Keywords||diagnostic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96986
--- Comment #6 from anlauf at gcc dot gnu.org ---
(In reply to kargl from comment #5)
>If the ENTRY statement is in a subroutine subprogram, an additional
>subroutine is defined by that subprogram. The name of the subroutine
&
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96381
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78746
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78746
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98507
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Component|fortran |libfortran
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89661
anlauf at gcc dot gnu.org changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92736
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88356
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |WAITING
CC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98577
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |INVALID
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78746
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86656
Bug 86656 depends on bug 78746, which changed state.
Bug 78746 Summary: charlen_03, charlen_10 ICE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78746
What|Removed |Added
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89891
Bug 89891 depends on bug 78746, which changed state.
Bug 78746 Summary: charlen_03, charlen_10 ICE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78746
What|Removed |Added
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89661
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89891
Bug 89891 depends on bug 89661, which changed state.
Bug 89661 Summary: FAIL: gfortran.dg/class_61.f90 -O (internal compiler
error)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89661
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60576
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|REOPENED|WAITING
CC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66366
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66366
--- Comment #12 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #11)
> The error vanishes if the typebound procedure is removed from the type
> declaration and the corresponding typebound call.
Or renaming the local in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93340
--- Comment #6 from anlauf at gcc dot gnu.org ---
Tentative patch: https://gcc.gnu.org/pipermail/fortran/2021-January/055589.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78746
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|REOPENED|WAITING
--- Comment #28 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78746
--- Comment #30 from anlauf at gcc dot gnu.org ---
(In reply to Dominique d'Humieres from comment #29)
> > There's no testcase named "pr78746.f90" in the testsuite.
>
> Ideed! My prx.f90 are in the tes
: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: anlauf at gcc dot gnu.org
Target Milestone: ---
The following invalid code exhibits valgrind issues during error recovery
(based on charlen_03.f90 which was removed from the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98661
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Keywords||error-recovery
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86656
Bug 86656 depends on bug 78746, which changed state.
Bug 78746 Summary: charlen_03, charlen_10 ICE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78746
What|Removed |Added
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78746
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89891
Bug 89891 depends on bug 78746, which changed state.
Bug 78746 Summary: charlen_03, charlen_10 ICE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78746
What|Removed |Added
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98661
--- Comment #2 from anlauf at gcc dot gnu.org ---
This has nothing to do with character at all. Same issue with:
program p
implicit none
type t
integer, allocatable :: x(n) ! { dg-error "must have a deferred shape" }
end ty
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98661
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: anlauf at gcc dot gnu.org
Target Milestone: ---
The following code is silently accepted even with -std=f95 ... -std=2018:
implicit none
namelist /NML/ x
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98686
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Keywords||diagnostic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98686
--- Comment #1 from anlauf at gcc dot gnu.org ---
F2018:
8.9 NAMELIST statement
(5) A namelist group object shall either be accessed by use or host association
or shall have its declared type, kind type parameters of the declared type, and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98661
--- Comment #6 from anlauf at gcc dot gnu.org ---
The commit in comment#4 unfortunately contained debugging stuff that should
never have been pushed. Thus reverted and created the new commit in comment#5.
Sorry for that.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93340
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98699
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Component|fortran |libgomp
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98661
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86656
Bug 86656 depends on bug 98661, which changed state.
Bug 98661 Summary: Valgrind errors during error recovery of invalid derived
type declarations
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98661
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89891
Bug 89891 depends on bug 98661, which changed state.
Bug 98661 Summary: Valgrind errors during error recovery of invalid derived
type declarations
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98661
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88124
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |WAITING
CC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91782
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91640
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85547
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98129
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Attachment #49687|0 |1
is obsolete
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98129
--- Comment #13 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #12)
> I had one (random?) failure with append_1.f90 which I am unable to reproduce.
Likely origin: parallel make -j4 check-fortran and
% grep -il o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86470
--- Comment #7 from anlauf at gcc dot gnu.org ---
Untested patch:
diff --git a/gcc/fortran/trans.c b/gcc/fortran/trans.c
index a2376917635..7699e98f6ea 100644
--- a/gcc/fortran/trans.c
+++ b/gcc/fortran/trans.c
@@ -689,9 +689,14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97272
--- Comment #11 from anlauf at gcc dot gnu.org ---
(In reply to Bill Long from comment #10)
> Still fails with 10.2.0. Can you say which release version will include the
> fix?
According to https://gcc.gnu.org/, gcc 10.2 was released i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70070
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70070
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33056
Bug 33056 depends on bug 70070, which changed state.
Bug 70070 Summary: ICE on initializing character data beyond min/max bound
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70070
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70913
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC|anlauf at gmx dot de |
--- Comment #8 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87568
--- Comment #2 from anlauf at gcc dot gnu.org ---
I cannot reproduce the error with r11-6901, but I still see it on 10-branch.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91862
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #5 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86470
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86470
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95682
--- Comment #2 from anlauf at gcc dot gnu.org ---
Adding some printout after initializing the t1%x(:),
do i = 1, size(t1%x)
print *, len_trim (t1%x(i)), t1%x(i)
end do
I get for gcc-8:
5 three
5 three
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99111
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Ever confirmed|0 |1
CC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99147
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2021-02-18
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99147
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99169
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Known to work||8.4.1
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99169
--- Comment #2 from anlauf at gcc dot gnu.org ---
Note/workaround: the {CLOBBER} disappears if the argument to set_i is declared
INOUT instead of OUT.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99169
--- Comment #3 from anlauf at gcc dot gnu.org ---
A conservative solution simply disables the clobber:
diff --git a/gcc/fortran/trans-expr.c b/gcc/fortran/trans-expr.c
index 103cb31c664..ce7bfaa89e8 100644
--- a/gcc/fortran/trans-expr.c
+++ b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99169
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99169
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99147
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99204
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|WAITING |NEW
CC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99206
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P4
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99206
--- Comment #2 from anlauf at gcc dot gnu.org ---
As a sidenote:
print *, len (reshape (['a'], [0]))
end
This prints 0 for gcc-11, and the correct value 1 for 10.2.1.
Do we screw up things during simplification?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99206
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99206
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99206
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99169
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99218
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Ever confirmed|0 |1
CC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99218
--- Comment #2 from anlauf at gcc dot gnu.org ---
Reduced testcase:
program play
implicit none
integer, parameter :: NCON = 1
integer, parameter :: NSTATE = 3
real,parameter :: ZERO = 0.0
real :: G(nCon,nState) = ZERO
real
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99218
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Known to fail||8.4.1
--- Comment #3 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99218
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Summary|matmul on temporary array |[8/9/19/11 Regression
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99218
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99218
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Summary|[8/9/19/11 Regression] |[8/9/10/11 Regression
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99257
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93340
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100273
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100273
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |9.4
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100274
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |9.4
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100274
--- Comment #2 from anlauf at gcc dot gnu.org ---
The patch in comment#1 would turn the ICE into an accepts-invalid, since
we would only get a warning instead of an error. This happens because
the character length check in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100274
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100218
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100154
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status
601 - 700 of 2659 matches
Mail list logo