https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103942
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106121
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=105691
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |10.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105813
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95107
--- Comment #9 from anlauf at gcc dot gnu.org ---
The issue can be studied by playing with option -fmax-stack-var-size=n.
-fno-automatic corresponds to n=0; using n=64 and higher lets the code compile.
There's something weird going on here.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95375
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=106108
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104430
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |WAITING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106089
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||kaiserkarl31 at yahoo dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105954
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105691
--- Comment #8 from anlauf at gcc dot gnu.org ---
Fixed on mainline so far.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103707
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2022-06-26
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105813
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106049
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106121
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95372
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105243
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=105243
--- Comment #10 from anlauf at gcc dot gnu.org ---
Submitted: https://gcc.gnu.org/pipermail/fortran/2022-June/057972.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106121
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=104684
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=104684
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Keywords||ice-on-valid-code
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106049
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=106047
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105986
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Ever confirmed|0 |1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105986
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=105986
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105986
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105954
--- Comment #3 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #2)
> Reduced testcase:
>
> integer, parameter :: m = sizeof(d) ! ICE for n < 1
In target-memory.cc we run into int_size_in_bytes(), which returns -12
for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105954
--- Comment #4 from anlauf at gcc dot gnu.org ---
Anyway, there's likely an ordering issue looking at array bounds and using
them. Moving the type decl to a module, the problem seems to disappear:
module m
implicit none
integer, parameter
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105954
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=105954
--- Comment #5 from anlauf at gcc dot gnu.org ---
The following patch fixes the ICE and regtests OK:
diff --git a/gcc/fortran/decl.cc b/gcc/fortran/decl.cc
index bd586e75008..3e04f45e9ac 100644
--- a/gcc/fortran/decl.cc
+++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105954
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101330
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=103590
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106353
--- Comment #3 from anlauf at gcc dot gnu.org ---
For code like
rhogvx=2
where we know that we initialize a full (and here contiguous) array, is
there something the frontend can do, e.g. to annotate that a collapse
of the loop nest is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101330
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101330
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=77652
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=103590
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=104313
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106331
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Summary|Whole array assignment of |[12/13 Regression] Whole
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103590
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=77652
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|WAITING
--- Comment #6 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103504
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106295
--- Comment #4 from anlauf at gcc dot gnu.org ---
I think the fix for PR83036 (INQUIRE specifier NEXTREC is a 4-byte integer,
should be 8), which changed the layout of struct st_parameter_inquire,
could explain what you observe.
I have no
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106209
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=103366
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=106209
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103504
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |10.5
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92805
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=92805
--- Comment #12 from anlauf at gcc dot gnu.org ---
Submitted: https://gcc.gnu.org/pipermail/fortran/2022-July/058023.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77652
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103504
--- Comment #2 from anlauf at gcc dot gnu.org ---
The ICE is avoided by:
diff --git a/gcc/fortran/interface.cc b/gcc/fortran/interface.cc
index 7ed6e13711f..f8a1720ea7e 100644
--- a/gcc/fortran/interface.cc
+++ b/gcc/fortran/interface.cc
@@
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104313
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=106402
--- Comment #1 from anlauf at gcc dot gnu.org ---
See also thread at: https://gcc.gnu.org/pipermail/fortran/2022-May/057860.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106410
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2022-07-22
Ever
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102818
--- Comment #1 from anlauf at gcc dot gnu.org ---
The proper function name is diagnosed after the following patch:
diff --git a/gcc/fortran/symbol.cc b/gcc/fortran/symbol.cc
index 7a80dfd063b..0d0221fc3c4 100644
--- a/gcc/fortran/symbol.cc
+++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105501
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2022-05-06
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105501
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=105473
--- Comment #5 from anlauf at gcc dot gnu.org ---
(In reply to Jerry DeLisle from comment #4)
> I see I no longer have change status on PRs. Evidently some of the address
> and login changes I have had to do in the process of changing my email
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105543
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105230
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=105526
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105526
Bug ID: 105526
Summary: [Coarray] Missing checks for arguments of type
TEAM_TYPE
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105501
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105501
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |13.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105526
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Ever confirmed|0 |1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78054
--- Comment #9 from anlauf at gcc dot gnu.org ---
(In reply to Thomas Koenig from comment #8)
> Fixed on trunk by
>
> https://gcc.gnu.org/pipermail/gcc-cvs/2022-April/362724.html .
Thomas,
you'd better re-read Steve's analysis.
Your patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105371
--- Comment #4 from anlauf at gcc dot gnu.org ---
The following untested hackish patch leads to the same answer for both cases:
diff --git a/gcc/fortran/simplify.cc b/gcc/fortran/simplify.cc
index 233cc42137f..abd93956217 100644
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105012
--- Comment #17 from anlauf at gcc dot gnu.org ---
(In reply to Richard Biener from comment #11)
> (In reply to Richard Biener from comment #10)
> > likely triggered by the INTENT(out), it looks like gfortran fails to
> > properly
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105012
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=103694
--- Comment #6 from anlauf at gcc dot gnu.org ---
Potential fix that regtests cleanly:
diff --git a/gcc/fortran/simplify.cc b/gcc/fortran/simplify.cc
index f992c31e5d7..3d2a68fa36a 100644
--- a/gcc/fortran/simplify.cc
+++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103694
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78054
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|WAITING
--- Comment #12 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103694
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106771
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=106771
--- Comment #4 from anlauf at gcc dot gnu.org ---
(In reply to federico from comment #3)
> Right: here is a version where the object is initialized:
>
> https://godbolt.org/z/o566cPG8P
>
> I also see that for the versions that compile (e.g.,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106771
--- Comment #2 from anlauf at gcc dot gnu.org ---
Playing a little, I found that the issue might be related to the elemental
function isa.
The following dumb replacement
function isa(this,i)
class(t), intent(in) :: this
integer,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106771
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|WAITING |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106684
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=106557
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=106684
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |INVALID
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106750
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2022-08-30
Ever
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106750
--- Comment #2 from anlauf at gcc dot gnu.org ---
If you need a workaround, replace:
j(i) = do_with_array(ts(choose)) ! [#1] MEMORY LEAK
by
j(i) = do_with_array([ts(choose)]) ! [#1] no more MEMORY LEAK
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99349
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=100245
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=99349
--- Comment #5 from anlauf at gcc dot gnu.org ---
(In reply to Steve Kargl from comment #4)
> The function is match_data_constant(), so we're looking for a
> constant. My patch simply removes the type checking as it is
> unimportant here, and a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106857
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106817
--- Comment #5 from anlauf at gcc dot gnu.org ---
(In reply to Mikael Morin from comment #4)
> With the testcase from comment #3, it becomes:
>
> a = {CLOBBER};
> D.4223 = a + 1;
> copy (, );
Right. And with -Wall one gets a bogus
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104314
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=100136
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100136
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Keywords||ice-on-valid-code
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106557
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100948
--- Comment #9 from anlauf at gcc dot gnu.org ---
(In reply to José Rui Faustino de Sousa from comment #6)
> Created attachment 51002 [details]
> Patch and changelog
I took a look at the attached patch.
While it does resolve the ICE on the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105012
--- Comment #25 from anlauf at gcc dot gnu.org ---
(In reply to Mikael Morin from comment #24)
> (In reply to anlauf from comment #22)
> >
> > The remaining problem from PR41453#c8 is the following code in
> > trans-expr.cc:
> >
> > (gdb) l
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105012
--- Comment #29 from anlauf at gcc dot gnu.org ---
(In reply to Mikael Morin from comment #28)
> With the following, I get the expected result.
> Indeed, with se->want_pointer set, gfc_conv_expr generates an address
> expression, so it has to be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105012
--- Comment #27 from anlauf at gcc dot gnu.org ---
(In reply to Mikael Morin from comment #26)
> (In reply to anlauf from comment #25)
> > (In reply to Mikael Morin from comment #24)
> > > (In reply to anlauf from comment #22)
> > > >
> > > >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105012
--- Comment #23 from anlauf at gcc dot gnu.org ---
(In reply to Mikael Morin from comment #21)
> (In reply to anlauf from comment #18)
> > Tentative patch, regtests cleanly but otherwise untested:
> >
> > diff --git a/gcc/fortran/trans-expr.cc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41453
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Component|middle-end |fortran
--- Comment #9 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105012
--- Comment #22 from anlauf at gcc dot gnu.org ---
(In reply to Richard Biener from comment #20)
> With your patch I still see
>
> __attribute__((fn spec (". r ")))
> real(kind=8) derfc (real(kind=8) & restrict x)
> {
> integer(kind=4) jint;
1001 - 1100 of 2164 matches
Mail list logo