https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95544
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95670
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2020-06-14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95689
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
CC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95689
--- Comment #3 from anlauf at gcc dot gnu.org ---
Patch submitted for review:
https://gcc.gnu.org/pipermail/fortran/2020-June/054525.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95687
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=95687
--- Comment #3 from anlauf at gcc dot gnu.org ---
Patch posted for review:
https://gcc.gnu.org/pipermail/fortran/2020-June/054527.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95688
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=95707
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2020-06-16
Ever
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95707
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=95687
--- Comment #4 from anlauf at gcc dot gnu.org ---
Updated / corrected patch posted for review:
https://gcc.gnu.org/pipermail/fortran/2020-June/054548.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95088
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95587
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=95587
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=95067
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P5
Severity|normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50410
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=94463
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=94463
--- Comment #3 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #2)
> If both files are combined into one, only the proper symbol is generated.
>
> Module read/write related?
Setting a breakpoint on mangled_ident
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50410
--- Comment #42 from anlauf at gcc dot gnu.org ---
(In reply to Dominique d'Humieres from comment #41)
> In my working tree I had the following patch
This still ICEs on comment#23 z1.
Slightly rewriting that case, one gets a reasonab
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50410
--- Comment #43 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #42)
> The following patch does the magic (not regtested):
>
> diff --git a/gcc/fortran/expr.c b/gcc/fortran/expr.c
> index 8daa7bb8d06..0a995e
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95826
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95827
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Priority
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95828
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=95587
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95689
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95687
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95688
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95707
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95826
--- Comment #2 from anlauf at gcc dot gnu.org ---
Patch posted for review:
https://gcc.gnu.org/pipermail/fortran/2020-June/054582.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95827
--- Comment #2 from anlauf at gcc dot gnu.org ---
Patch posted for review:
https://gcc.gnu.org/pipermail/fortran/2020-June/054583.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95877
--- Comment #1 from anlauf at gcc dot gnu.org ---
(In reply to Bill Seurer from comment #0)
> g:84323d9fa7526496d844f167f6353e0ec12279e8, r9-8693
>
> This same error occurs on both gcc 8 and 9. Bad backport maybe?
I do not get this
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95828
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95828
--- Comment #3 from anlauf at gcc dot gnu.org ---
Patch posted: https://gcc.gnu.org/pipermail/fortran/2020-June/054604.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95689
--- Comment #11 from anlauf at gcc dot gnu.org ---
Reverted on 8- and 9-branch, since not a critical regression, and a clean
backport would need a manual backport of a series of other fixes.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95877
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #2 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93337
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=93337
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=93423
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=95827
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95881
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=95881
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95828
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95826
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95881
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95880
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=95880
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=77871
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=71706
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=95340
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95880
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Summary|[9/10/11 Regression] ICE in |[9 Regression] ICE in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95979
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P4
Last reconfirmed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95980
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95978
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=95978
--- Comment #3 from anlauf at gcc dot gnu.org ---
The obvious patch
diff --git a/gcc/fortran/decl.c b/gcc/fortran/decl.c
index ac1f63f66e0..f38def4c291 100644
--- a/gcc/fortran/decl.c
+++ b/gcc/fortran/decl.c
@@ -728,7 +728,7 @@ gfc_match_data
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95978
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=95978
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71706
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Summary|[8/9/10/11 Regression] |[8/9 Regression] [Coarray
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82314
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=88379
--- Comment #5 from anlauf at gcc dot gnu.org ---
NULL pointer dereference fix, committed to master as obvious:
https://gcc.gnu.org/pipermail/fortran/2020-June/054665.html
Backports pending.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88379
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96018
--- Comment #3 from anlauf at gcc dot gnu.org ---
You are not using HDF5's "native" Fortran interface directly, but a
clumsy way with c_f_pointer to obscure your code. Any reason for that?
Have you considered using RESHAPE for w
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96018
--- Comment #5 from anlauf at gcc dot gnu.org ---
(In reply to martin.schlipf from comment #4)
> Finally, I reproduced it with gfortran 9.3.0 + hdf 1.12.0 and gfortran 10.0
> + hdf 1.10.4. With older versions of gfortran 7.3.0 it does not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95880
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52622
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |WAITING
Priority
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71706
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27766
Bug 27766 depends on bug 71706, which changed state.
Bug 71706 Summary: [8/9 Regression] [Coarray] ICE on using sync images with
integer(kind<>4), with -fcoarray=lib -fcheck=bounds
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71706
Wh
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83700
Bug 83700 depends on bug 71706, which changed state.
Bug 71706 Summary: [8/9 Regression] [Coarray] ICE on using sync images with
integer(kind<>4), with -fcoarray=lib -fcheck=bounds
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71706
Wh
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88379
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Summary|[8/9/10/11 Regression] |[8/9 Regression] [Coarray
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95709
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=96041
--- Comment #1 from anlauf at gcc dot gnu.org ---
(In reply to Bill Seurer from comment #0)
> f951: internal compiler error: Segmentation fault
> 0x10be671b crash_signal
> /home/seurer/gcc/git/gcc-test/gcc/toplev.c:328
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96041
--- Comment #4 from anlauf at gcc dot gnu.org ---
(In reply to Dominique d'Humieres from comment #3)
> From several runs
>
> frame #0: 0x0001000f11ed f951`gfc_free_namespace(gfc_namespace*)
> [inlined] free_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93423
--- Comment #5 from anlauf at gcc dot gnu.org ---
Backports will have to wait until PR96041 is resolved.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88379
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87477
Bug 87477 depends on bug 88379, which changed state.
Bug 88379 Summary: [8/9 Regression] [Coarray] ICE with allocatable coarray,
class and associate in resolve_assoc_var, at fortran/resolve.c:8750
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=8837
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83700
Bug 83700 depends on bug 88379, which changed state.
Bug 88379 Summary: [8/9 Regression] [Coarray] ICE with allocatable coarray,
class and associate in resolve_assoc_var, at fortran/resolve.c:8750
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=8837
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89574
--- Comment #7 from anlauf at gcc dot gnu.org ---
Two slightly reduced testcase variants that ICE with current master:
% cat pr89574-red1.f90
module mod
contains
subroutine init
end subroutine
end module mod
module init
use mod, only
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96041
--- Comment #6 from anlauf at gcc dot gnu.org ---
On x86_64 I never reach symbol.c:2662, since the code returns from line 2659.
This the closest I get to your backtrace:
Breakpoint 2, free_st_labels (label=0x0) at
../../gcc-trunk/gcc/fortran
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96086
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=96086
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95980
--- Comment #6 from anlauf at gcc dot gnu.org ---
Created attachment 48839
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48839&action=edit
Patch, part 2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95980
--- Comment #7 from anlauf at gcc dot gnu.org ---
(In reply to Dominique d'Humieres from comment #5)
> AFAICT the patch fixes the ICE for z2.f90, but not for z1.f90.
You're right. I got lost in trying to work on too many PRs.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96071
--- Comment #2 from anlauf at gcc dot gnu.org ---
Isn't that almost exactly a dup of PR92967? (Except for integer <-> real)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95980
--- Comment #11 from anlauf at gcc dot gnu.org ---
(In reply to Dominique d'Humieres from comment #10)
> > Confirmed on preliminary tests (pr86551), full tests in progress: results
> > tomorrow).
>
> Regtested without
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95980
--- Comment #12 from anlauf at gcc dot gnu.org ---
(In reply to Steve Kargl from comment #9)
> This has been true since I started working on gfortran some
> 15+ years ago. Much of the code is written assuming a correctly
> writte
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96084
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2020-07-07
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96041
--- Comment #8 from anlauf at gcc dot gnu.org ---
(In reply to Dominique d'Humieres from comment #7)
> f951`gfc_resolve_formal_arglist(proc=0x00014301fbb0) at resolve.c:313:18
> frame #2: 0x0001000eb283
Setting a breakpoi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93337
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96085
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=96085
--- Comment #3 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #2)
That one produces a strange regression with pr50392.f.
Patch that regtests fine:
diff --git a/gcc/fortran/resolve.c b/gcc/fortran/resolve.c
index 223de91
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95980
--- Comment #15 from anlauf at gcc dot gnu.org ---
(In reply to G. Steinmetz from comment #14)
> Even the standards changed, too.
> F2018 has the audacity to demand chapter 4.2, item 2.
"(2) it contains the capability to detect and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95709
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96085
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89574
--- Comment #8 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #7)
> Since changing "module init" to "module init1" avoid the issue in all
> cases, this lookslike a namespace / symbol issue.
I spen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93473
--- Comment #11 from anlauf at gcc dot gnu.org ---
Anything left to do?
I looked at the gcc-testresults, and it appears things are fixed now,
e.g. for Solaris or aarch64.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89574
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=89574
--- Comment #10 from anlauf at gcc dot gnu.org ---
Patch: https://gcc.gnu.org/pipermail/fortran/2020-July/054744.html
: enhancement
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: anlauf at gcc dot gnu.org
Target Milestone: ---
Consider the following code:
module mod
contains
subroutine init
end subroutine
end module
module init
use mod
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96224
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93592
--- Comment #8 from anlauf at gcc dot gnu.org ---
(In reply to Dominique d'Humieres from comment #7)
> Could someone used to git commit the fix and the tests and back port them to
> all the active branches?
I think the normal procedu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92091
--- Comment #3 from anlauf at gcc dot gnu.org ---
(In reply to Dominique d'Humieres from comment #2)
> Am I correct to understand that #include is handled by the preprocessor?
Yes.
Other compilers always show the path to the included
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70913
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
101 - 200 of 2407 matches
Mail list logo