https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89375
--- Comment #5 from Fritz Reese ---
Thanks Dominiq.
On Wed, Apr 3, 2019, 05:02 dominiq at lps dot ens.fr <
gcc-bugzi...@gcc.gnu.org> wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89375
>
> Dominique d'Humieres changed:
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82511
--- Comment #5 from Fritz Reese ---
Nice! That should probably not compile. There is some trickiness because it
is valid to create a RECORD variable with the same name as a STRUCTURE.
I’ll get on that as well.
On Fri, Oct 13, 2017, 13:49 sgk at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77584
Fritz Reese changed:
What|Removed |Added
CC||fritzoreese at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77584
--- Comment #4 from Fritz Reese ---
Yes, fixed in r240230, I can't change the bug status myself or I would've
https://gcc.gnu.org/ml/fortran/2016-09/msg00105.html
On Thu, Sep 29, 2016, 21:06 dominiq at lps dot ens.fr <
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77764
Fritz Reese changed:
What|Removed |Added
CC||fritzoreese at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77782
--- Comment #2 from Fritz Reese ---
https://gcc.gnu.org/ml/fortran/2016-09/msg00189.html
Patch submitted
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77584
--- Comment #1 from Fritz Reese ---
Created attachment 39618
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39618=edit
Patch for PR 77584
The attached patch fixes the issue.
2016-09-14 Fritz Reese
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77327
--- Comment #7 from Fritz Reese ---
(In reply to Vittorio Zecca from comment #5)
> The test case you propose, dec_structure_13.f90, does not trigger the asan
> memory checker.
Sorry if it was unclear, the new testcase dec_structure_13.f90 tests
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77327
--- Comment #3 from Fritz Reese ---
> interface.c:403 is
> if ( (d1 && (d1->attr.flavor == FL_STRUCT || d1->attr.flavor == FL_UNION)
>
> and I believe d->attr.flavor is the item used after freed.
This is correct, and the reason is clear when
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77327
Fritz Reese changed:
What|Removed |Added
CC||fritzoreese at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71523
Fritz Reese changed:
What|Removed |Added
CC||fritzoreese at gmail dot com
--- Comment
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: fritzoreese at gmail dot com
Target Milestone: ---
This bug is similar to pr41860. When a variable becomes static due to being
larger than -fmax-stack-var-size
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71047
--- Comment #4 from Fritz Reese ---
See https://gcc.gnu.org/ml/fortran/2016-05/msg00032.html for the fix.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56226
--- Comment #29 from Fritz Reese ---
(In reply to Andreas Schwab from comment #25)
> FAIL: gfortran.dg/dec_union_4.f90 -O0 execution test
> FAIL: gfortran.dg/dec_union_4.f90 -O1 execution test
> FAIL: gfortran.dg/dec_union_4.f90 -O2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56226
--- Comment #13 from Fritz Reese ---
I actually have a fairly in-depth set of testcases as part of the patch (based
on lots of legacy code). More are of course welcome, but check out what I've
already added as a starting point.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56226
--- Comment #9 from Fritz Reese ---
I've finally submitted my patches for a -fdec-structure option which enables
STRUCTURE/RECORD and UNION/MAP support:
https://gcc.gnu.org/ml/fortran/2016-03/msg2.html
I have (4) patches, and had to submit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56226
--- Comment #7 from Fritz Reese fritzoreese at gmail dot com ---
FWIW I have the patches ready against the gcc-5.0.0 dev trunk, I'm just waiting
on my employer's lawyer, who has been on vacation for several weeks, to sort
out the legal issues
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62174
--- Comment #3 from Fritz Reese fritzoreese at gmail dot com ---
Patches should go to the gcc-patches at gcc.gnu.org mailing list (and in
case of Fortran FE patches also CC fortran at gcc.gnu.org ml). That is
where patch review happens
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: fritzoreese at gmail dot com
It seems with gcc-4.8.3 -fno-automatic prevents initializers from being applied
to automatic variables. The following does
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62309
Fritz Reese fritzoreese at gmail dot com changed:
What|Removed |Added
CC||fritzoreese
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: fritzoreese at gmail dot com
Created attachment 33353
-- https://gcc.gnu.org/bugzilla/attachment.cgi?id=33353action=edit
Proposed patch for the described problem
The typespecs
21 matches
Mail list logo