From: "Martin Liška" <mliska@suse.cz>
To: Xi Ruoyao <xry111@xry111.site>
Cc: gcc@gcc.gnu.org, fortran@gcc.gnu.org,
Richard Biener <rguenther@suse.de>,
gcc-patches@gcc.gnu.org, Lulu Cheng <chenglulu@loongson.cn>,
Jakub Jelinek <jakub@redhat.com>
Subject: Re: GCC 13.0.0 Status Report (2022-11-14), Stage 3 in effect now
Date: Tue, 15 Nov 2022 11:02:53 +0100 [thread overview]
Message-ID: <ef918714-da26-a45c-f050-da8e77e2b276@suse.cz> (raw)
In-Reply-To: <b55c1caaf82d001ef085029fb87423c88bcbf4a6.camel@xry111.site>
On 11/14/22 18:21, Xi Ruoyao wrote:
> Hi Martin,
>
Hello.
> Is it allowed to merge libsanitizer from LLVM in stage 3? If not I'd
> like to cherry pick some commits from LLVM [to fix some stupid errors
> I've made in LoongArch libasan :(].
I'm sorry but I was really busy with the porting of the documentation to Sphinx.
Anyway, yes, we should make one one libsanitizer merge, but RM should likely
approve it: Richi, Jakub, do you support it?
Thanks,
Martin
>
> On Mon, 2022-11-14 at 13:21 +0000, Richard Biener via Gcc-patches wrote:
>> Status
>> ======
>>
>> The GCC development branch which will become GCC 13 is now in
>> bugfixing mode (Stage 3) until the end of Jan 15th.
>>
>> As usual the first weeks of Stage 3 are used to feature patches
>> posted late during Stage 1. At some point unreviewed features
>> need to be postponed for the next Stage 1.
>>
>>
>> Quality Data
>> ============
>>
>> Priority # Change from last report
>> -------- --- -----------------------
>> P1 33
>> P2 473
>> P3 113 + 29
>> P4 253 + 6
>> P5 25
>> -------- --- -----------------------
>> Total P1-P3 619 + 29
>> Total 897 + 35
>>
>>
>> Previous Report
>> ===============
>>
>> https://gcc.gnu.org/pipermail/gcc/2022-October/239690.html
>
next prev parent reply other threads:[~2022-11-15 10:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 13:21 Richard Biener
2022-11-14 17:21 ` Xi Ruoyao
2022-11-15 10:02 ` Martin Liška [this message]
2022-11-15 10:07 ` Jakub Jelinek
2022-11-15 12:49 ` Martin Liška
2022-11-15 13:02 ` Jakub Jelinek
2022-11-15 15:47 ` libsanitizer: sync from master Martin Liška
2023-04-26 13:51 ` Martin Liška
2023-04-26 18:31 ` Florian Weimer
2023-04-26 19:50 ` Bernhard Reutner-Fischer
2023-04-26 20:26 ` Martin Liška
2023-04-28 9:23 ` Florian Weimer
2023-04-28 18:33 ` Bernhard Reutner-Fischer
2023-04-30 7:58 ` Martin Liška
2023-04-26 19:23 ` H.J. Lu
2023-04-26 20:24 ` Martin Liška
2023-04-26 23:37 ` H.J. Lu
2023-04-27 1:31 ` H.J. Lu
2023-04-30 16:01 ` Andrew Pinski
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=ef918714-da26-a45c-f050-da8e77e2b276@suse.cz \
--to=mliska@suse.cz \
--cc=chenglulu@loongson.cn \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=rguenther@suse.de \
--cc=xry111@xry111.site \
/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).