public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/88286] [OOP] gfortran reports conflicting intent(in) with an intent(in) declared class variable
       [not found] <bug-88286-4@http.gcc.gnu.org/bugzilla/>
@ 2023-08-01 20:19 ` anlauf at gcc dot gnu.org
  2023-08-02 16:51 ` kargl at gcc dot gnu.org
  2023-08-13 20:22 ` anlauf at gcc dot gnu.org
  2 siblings, 0 replies; 3+ messages in thread
From: anlauf at gcc dot gnu.org @ 2023-08-01 20:19 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88286

anlauf at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Known to work|                            |12.3.0, 13.1.0, 14.0
      Known to fail|                            |11.4.1
             Status|NEW                         |WAITING

--- Comment #2 from anlauf at gcc dot gnu.org ---
Appears fixed in 12-branch and later.  Adding known-to work.

Can we close this one?

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug fortran/88286] [OOP] gfortran reports conflicting intent(in) with an intent(in) declared class variable
       [not found] <bug-88286-4@http.gcc.gnu.org/bugzilla/>
  2023-08-01 20:19 ` [Bug fortran/88286] [OOP] gfortran reports conflicting intent(in) with an intent(in) declared class variable anlauf at gcc dot gnu.org
@ 2023-08-02 16:51 ` kargl at gcc dot gnu.org
  2023-08-13 20:22 ` anlauf at gcc dot gnu.org
  2 siblings, 0 replies; 3+ messages in thread
From: kargl at gcc dot gnu.org @ 2023-08-02 16:51 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88286

kargl at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kargl at gcc dot gnu.org

--- Comment #3 from kargl at gcc dot gnu.org ---
(In reply to anlauf from comment #2)
> Appears fixed in 12-branch and later.  Adding known-to work.
> 
> Can we close this one?

I think the answer is "yes".  It comes down to "too many bugs and too few
contributors".  If someone can identify the commit that fixed this bug, then by
all means it can be back-ported.  It's unclear to me if it is worth the effort
to find the commit.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug fortran/88286] [OOP] gfortran reports conflicting intent(in) with an intent(in) declared class variable
       [not found] <bug-88286-4@http.gcc.gnu.org/bugzilla/>
  2023-08-01 20:19 ` [Bug fortran/88286] [OOP] gfortran reports conflicting intent(in) with an intent(in) declared class variable anlauf at gcc dot gnu.org
  2023-08-02 16:51 ` kargl at gcc dot gnu.org
@ 2023-08-13 20:22 ` anlauf at gcc dot gnu.org
  2 siblings, 0 replies; 3+ messages in thread
From: anlauf at gcc dot gnu.org @ 2023-08-13 20:22 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88286

anlauf at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|---                         |12.3

--- Comment #4 from anlauf at gcc dot gnu.org ---
Closing then.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2023-08-13 20:22 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <bug-88286-4@http.gcc.gnu.org/bugzilla/>
2023-08-01 20:19 ` [Bug fortran/88286] [OOP] gfortran reports conflicting intent(in) with an intent(in) declared class variable anlauf at gcc dot gnu.org
2023-08-02 16:51 ` kargl at gcc dot gnu.org
2023-08-13 20:22 ` 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).