public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: Xi Ruoyao <xry111@xry111.site>,
	gcc@gcc.gnu.org, fortran@gcc.gnu.org,
	Richard Biener <rguenther@suse.de>,
	gcc-patches@gcc.gnu.org, Lulu Cheng <chenglulu@loongson.cn>
Subject: Re: GCC 13.0.0 Status Report (2022-11-14), Stage 3 in effect now
Date: Tue, 15 Nov 2022 14:02:54 +0100	[thread overview]
Message-ID: <Y3ON/rrJxiHc7/r+@tucnak> (raw)
In-Reply-To: <6a8c0966-139a-1536-4ef3-ec99542bdf02@suse.cz>

On Tue, Nov 15, 2022 at 01:49:36PM +0100, Martin Liška wrote:
> On 11/15/22 11:07, Jakub Jelinek wrote:
> > On Tue, Nov 15, 2022 at 11:02:53AM +0100, Martin Liška wrote:
> >>> 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?
> > 
> > Could you please prepare a patch, so that we can see how much actually
> > changed and decide based on that whether to go for a merge or cherry-picking
> > one or more commits?
> 
> Sure, there it is. There's a minor change in output format that I address in 0003 patch.
> 
> Apart from that, I was able to run all tests on x86_64-linux-gnu.
> Patch statistics:
>  46 files changed, 524 insertions(+), 252 deletions(-)
> 
> I'm running build on ppc64le and if you're fine, I'm going to finish
> a proper libsanitizer testing procedure.

Ok.

	Jakub


  reply	other threads:[~2022-11-15 13:03 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
2022-11-15 10:07     ` Jakub Jelinek
2022-11-15 12:49       ` Martin Liška
2022-11-15 13:02         ` Jakub Jelinek [this message]
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=Y3ON/rrJxiHc7/r+@tucnak \
    --to=jakub@redhat.com \
    --cc=chenglulu@loongson.cn \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=mliska@suse.cz \
    --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).