public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/87659] Memory corruption in array component of intent(in) unlimited polymorphic with optimization
[not found] <bug-87659-4@http.gcc.gnu.org/bugzilla/>
@ 2022-10-08 20:39 ` mikael at gcc dot gnu.org
2022-10-17 18:33 ` anlauf at gcc dot gnu.org
2022-10-17 20:36 ` anlauf at gcc dot gnu.org
2 siblings, 0 replies; 3+ messages in thread
From: mikael at gcc dot gnu.org @ 2022-10-08 20:39 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87659
Mikael Morin <mikael at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mikael at gcc dot gnu.org
--- Comment #3 from Mikael Morin <mikael at gcc dot gnu.org> ---
Seems to work now...
^ permalink raw reply [flat|nested] 3+ messages in thread* [Bug fortran/87659] Memory corruption in array component of intent(in) unlimited polymorphic with optimization
[not found] <bug-87659-4@http.gcc.gnu.org/bugzilla/>
2022-10-08 20:39 ` [Bug fortran/87659] Memory corruption in array component of intent(in) unlimited polymorphic with optimization mikael at gcc dot gnu.org
@ 2022-10-17 18:33 ` anlauf at gcc dot gnu.org
2022-10-17 20:36 ` anlauf at gcc dot gnu.org
2 siblings, 0 replies; 3+ messages in thread
From: anlauf at gcc dot gnu.org @ 2022-10-17 18:33 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87659
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to fail| |10.2.1, 11.3.0, 7.5.0,
| |8.5.0, 9.5.0
Status|NEW |WAITING
Known to work| |10.4.1, 11.3.1, 12.2.1,
| |13.0
--- Comment #4 from anlauf at gcc dot gnu.org ---
Adding several known-to-work/known-to-fail versions.
Possibly fixed by one of Jose's patches that was recently committed and
backported down to 10. (Could it be a dup of pr100132?)
^ permalink raw reply [flat|nested] 3+ messages in thread* [Bug fortran/87659] Memory corruption in array component of intent(in) unlimited polymorphic with optimization
[not found] <bug-87659-4@http.gcc.gnu.org/bugzilla/>
2022-10-08 20:39 ` [Bug fortran/87659] Memory corruption in array component of intent(in) unlimited polymorphic with optimization mikael at gcc dot gnu.org
2022-10-17 18:33 ` anlauf at gcc dot gnu.org
@ 2022-10-17 20:36 ` anlauf at gcc dot gnu.org
2 siblings, 0 replies; 3+ messages in thread
From: anlauf at gcc dot gnu.org @ 2022-10-17 20:36 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87659
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |anlauf at gcc dot gnu.org
Status|WAITING |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #5 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #4)
> Adding several known-to-work/known-to-fail versions.
>
> Possibly fixed by one of Jose's patches that was recently committed and
> backported down to 10. (Could it be a dup of pr100132?)
Yep, reverting that patch re-introduces the bug. Marking as dup.
*** This bug has been marked as a duplicate of bug 100132 ***
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-10-17 20:36 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-87659-4@http.gcc.gnu.org/bugzilla/>
2022-10-08 20:39 ` [Bug fortran/87659] Memory corruption in array component of intent(in) unlimited polymorphic with optimization mikael at gcc dot gnu.org
2022-10-17 18:33 ` anlauf at gcc dot gnu.org
2022-10-17 20:36 ` anlauf at gcc dot gnu.org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).