public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tobias Burnus <tobias@codesourcery.com>
To: "José Rui Faustino de Sousa" <jrfsousa@gmail.com>,
	fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org
Cc: Sandra Loosemore <sandra@codesourcery.com>
Subject: José's pending bind(C) patches / status (was: Re: [Patch, fortran V3] PR fortran/100683 - Array initialization refuses valid)
Date: Fri, 22 Oct 2021 09:42:41 +0200	[thread overview]
Message-ID: <327ebcb4-8502-ab31-ffda-e0be0740fcfc@codesourcery.com> (raw)
In-Reply-To: <01c32a3d-7a33-1866-667c-04689c0ae173@gmail.com>

Hi José, hi all,

especially since my patch which moved the descriptor conversion from
libgfortran to gfortran is in, I wonder whether there are still patches
to be applied and useful testcases; I assume there are more issues in
Bugzilla, especially as I filled myself some (often related to
polymorphism or assumed rank). While I (and also Sandra) try to resolve
some bugs and look at testcases:

it would be helpful if others – in particular José – could check
whether: (a) PRs can be now closed, (b) testcases exist which still
should be added, (c) patches exist which still are applicable (even if
they need to be revised). (Partial/full list below.)

I hope that we can really cleanup this backlog – and possibly fix also
some of the remaining bugs before GCC 12 is released!

And kudos to José for the bug reports, testcases and patches – and sorry
for slow reviews. I hope we resolve the pending issues and be quicker in
future.

Tobias

PS: Old and probably current but incomplete pending patch list:

On 21.06.21 17:21, José Rui Faustino de Sousa wrote:
> On 21/06/21 12:37, Tobias Burnus wrote:
>> Thus: Do you have a list of patches pending review?
>
> https://gcc.gnu.org/pipermail/fortran/2021-April/055924.html
>
> https://gcc.gnu.org/pipermail/fortran/2021-April/055933.html
>
> https://gcc.gnu.org/pipermail/fortran/2021-June/056168.html
>
> https://gcc.gnu.org/pipermail/fortran/2021-June/056167.html
>
> https://gcc.gnu.org/pipermail/fortran/2021-June/056163.html
>
> https://gcc.gnu.org/pipermail/fortran/2021-June/056162.html
>
> https://gcc.gnu.org/pipermail/fortran/2021-June/056155.html
>
> https://gcc.gnu.org/pipermail/fortran/2021-June/056154.html
>
> https://gcc.gnu.org/pipermail/fortran/2021-June/056152.html
>
> https://gcc.gnu.org/pipermail/fortran/2021-June/056159.html
>
> https://gcc.gnu.org/pipermail/fortran/2021-April/055982.html
>
> https://gcc.gnu.org/pipermail/fortran/2021-April/055949.html
>
> https://gcc.gnu.org/pipermail/fortran/2021-April/055946.html
>
> https://gcc.gnu.org/pipermail/fortran/2021-April/055934.html
>
> https://gcc.gnu.org/pipermail/fortran/2021-June/056169.html
>
> https://gcc.gnu.org/pipermail/fortran/2021-April/055921.html
>
> I am not 100% sure this is all of them but it should be most.
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955

  parent reply	other threads:[~2021-10-22  7:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-17 19:34 [Patch, fortran V3] PR fortran/100683 - Array initialization refuses valid José Rui Faustino de Sousa
2021-06-21 12:37 ` Tobias Burnus
2021-06-21 15:21   ` José Rui Faustino de Sousa
2021-06-21 18:27     ` Paul Richard Thomas
2021-10-22  7:42     ` Tobias Burnus [this message]
2021-10-22  8:19       ` José's pending bind(C) patches / status (was: Re: [Patch, fortran V3] PR fortran/100683 - Array initialization refuses valid) Paul Richard Thomas
2021-10-22 13:06       ` Tobias Burnus
2021-10-22 20:29         ` Harald Anlauf
2021-10-22 20:36         ` Harald Anlauf
2021-10-22 20:44         ` Harald Anlauf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=327ebcb4-8502-ab31-ffda-e0be0740fcfc@codesourcery.com \
    --to=tobias@codesourcery.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jrfsousa@gmail.com \
    --cc=sandra@codesourcery.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).