public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: fortran <fortran@gcc.gnu.org>
Subject: Re: GCC 10.2.1 Status Report (2021-03-19)
Date: Fri, 19 Mar 2021 18:57:32 +0000	[thread overview]
Message-ID: <CAGkQGiJCD3LBo1sTG7+E=CDnKpUnbm50Q6RPjwD7mHW0LfOh9w@mail.gmail.com> (raw)
In-Reply-To: <a818f159-85ec-622e-6545-ed3d0efa1c32@codesourcery.com>

Hi Tobias,

I'll do the reviews for you tomorrow morning. Right now my brain has turned
to mush after an excess of online meetings :-(

I'll take a look through my PRs to see what might need pushing onto
10-branch.

Cheers

Paul


On Fri, 19 Mar 2021 at 14:15, Tobias Burnus <tobias@codesourcery.com> wrote:

> FYI.
>
> On my side, I would like to backport the following patch, which is still
> pending preview:
> https://gcc.gnu.org/pipermail/gcc-patches/2021-March/566890.html
> (*PING*: Re: [Patch] Fortran: Fix func decl mismatch [PR93660])
>
> and possible the following patch as well, also pending review:
> https://gcc.gnu.org/pipermail/gcc-patches/2021-March/566956.html
> ([Patch] Fortran: Fix intrinsic null() handling [PR99651])
>
> Does anyone else have patches which still have to be reviewed?
>
> Tobias
>
> -------- Forwarded Message --------
> Subject:        GCC 10.2.1 Status Report (2021-03-19)
> Date:   Fri, 19 Mar 2021 14:17:45 +0100
> From:   Richard Biener <rguenther@suse.de>
> Reply-To:       gcc@gcc.gnu.org
> To:     gcc@gcc.gnu.org
> CC:     gcc-patches@gcc.gnu.org
>
>
>
> Status
> ======
>
> The GCC 10 branch is open for regression and documentation fixes.
> It's time to do the GCC 10.3 release and barring arrival of P1
> priority regressions the plan is to do a release candidate in
> two weeks, around Mar 31th with a release following a week later.
>
> Please see to backport regression fixes that went to trunk where
> appropriate and verify your target is in good health. Report any
> problems to bugzilla.
>
>
> Quality Data
> ============
>
> Priority # Change from last report
> -------- --- -----------------------
> P1 1 + 1
> P2 353 + 134
> P3 30 - 27
> P4 176
> P5 23 + 1
> -------- --- -----------------------
> Total P1-P3 384 + 108
> Total 583 + 109
>
>
> Previous Report
> ===============
>
> https://gcc.gnu.org/pipermail/gcc/2020-July/233214.html
> -----------------
> Mentor Graphics (Deutschland) GmbH, Arnulfstrasse 201, 80634 München
> Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Frank
> Thürauf
>


-- 
"If you can't explain it simply, you don't understand it well enough" -
Albert Einstein

      reply	other threads:[~2021-03-19 18:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <nycvar.YFH.7.76.2103191416580.17979@zhemvz.fhfr.qr>
2021-03-19 14:15 ` Fwd: " Tobias Burnus
2021-03-19 18:57   ` Paul Richard Thomas [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='CAGkQGiJCD3LBo1sTG7+E=CDnKpUnbm50Q6RPjwD7mHW0LfOh9w@mail.gmail.com' \
    --to=paul.richard.thomas@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=tobias@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).