public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: dhumieres.dominique@free.fr
To: "José Rui Faustino de Sous" <jrfsousa@gmail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, fortran@gcc.gnu.org
Subject: Re: [Patch, fortran V3] PR fortran/100683 - Array initialization refuses valid (list of pending patches)
Date: Wed, 23 Jun 2021 16:20:46 +0200	[thread overview]
Message-ID: <f7d79db7d63dab7474ed19b8df19a866@free.fr> (raw)
In-Reply-To: <4ec87b2fa0fd739200fa540e868d6212@free.fr>

Hi José,

> > Thus: Do you have a list of patches pending review?

> https://gcc.gnu.org/pipermail/fortran/2021-April/055924.html

PRs 100029 and 100040. I have the patch in my working tree
for a long time. It works as expected. OK to commit.

> https://gcc.gnu.org/pipermail/fortran/2021-April/055933.html

PRs 100097 and 100098. New patch at

https://gcc.gnu.org/pipermail/fortran/2021-June/056169.html

OK to commit the new patch.

> https://gcc.gnu.org/pipermail/fortran/2021-June/056168.html

PR 96870.

> https://gcc.gnu.org/pipermail/fortran/2021-June/056167.html

PR 96724. OK to commit.

> https://gcc.gnu.org/pipermail/fortran/2021-June/056163.html

PRs 93308, 93963, 94327, 94331, and 97046.
Already OKed at
https://gcc.gnu.org/pipermail/fortran/2021-June/056184.html
and
https://gcc.gnu.org/pipermail/fortran/2021-June/056193.html

> https://gcc.gnu.org/pipermail/fortran/2021-June/056162.html

PR 94104.

> https://gcc.gnu.org/pipermail/fortran/2021-June/056155.html

PR 100948.

> https://gcc.gnu.org/pipermail/fortran/2021-June/056154.html

PRs 100906, 100907, 100911, 100914, 100915, and 100916.
Tis patch works for me when applied to GCC12 (not GCC11)
but seems to conflict with the patch for
PRs 93308, 93963, 94327, 94331, and 97046.

> https://gcc.gnu.org/pipermail/fortran/2021-June/056152.html

PR 10148.

> https://gcc.gnu.org/pipermail/fortran/2021-June/056159.html

PR 92621.

> https://gcc.gnu.org/pipermail/fortran/2021-April/055982.html

PR 100245.

> https://gcc.gnu.org/pipermail/fortran/2021-April/055949.html

PR 100136.

> https://gcc.gnu.org/pipermail/fortran/2021-April/055946.html

PR 100132.

> https://gcc.gnu.org/pipermail/fortran/2021-April/055934.html

PR 100103.

> https://gcc.gnu.org/pipermail/fortran/2021-June/056169.html

PRs 100097 and 100098. OK for me.

> https://gcc.gnu.org/pipermail/fortran/2021-April/055921.html

PRs 100024 and 100025. OK for me.

Thanks for the great work, but please don't forget to mark the PRs
as ASSIGNED and don't hesitate to PING after a week.

Dominique


      reply	other threads:[~2021-06-23 14:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03 15:04 [Patch, fortran] PR fortran/100120/100816/100818/100819/100821 problems raised by aggregate data types dhumieres.dominique
2021-06-04 15:24 ` Paul Richard Thomas
2021-06-05 12:40   ` dhumieres.dominique
2021-06-06 17:58     ` Re:[Patch, fortran] PR fortran/93308/93963/94327/94331/97046 problems raised by descriptor handling dhumieres.dominique
2021-06-19 10:57       ` [Patch, fortran v2] " dhumieres.dominique
2021-06-19 11:00         ` [Patch, fortran V3] PR fortran/100683 - Array initialization refuses valid dhumieres.dominique
2021-06-23 14:20           ` dhumieres.dominique [this message]

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=f7d79db7d63dab7474ed19b8df19a866@free.fr \
    --to=dhumieres.dominique@free.fr \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jrfsousa@gmail.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).