public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: Jakub Jelinek <jakub@redhat.com>
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: libsanitizer: sync from master
Date: Tue, 15 Nov 2022 16:47:13 +0100	[thread overview]
Message-ID: <02a9e4ef-4d83-e4c4-cfeb-5e94fe63f1b3@suse.cz> (raw)
In-Reply-To: <Y3ON/rrJxiHc7/r+@tucnak>

Hi.

I've just pushed libsanitizer update that was tested on x86_64-linux and ppc64le-linux systems.
Moreover, I run bootstrap on x86_64-linux and checked ABI difference with abidiff.

Pushed as r13-4068-g3037f11fb86eda.

Cheers,
Martin

  reply	other threads:[~2022-11-15 15:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14 13:21 GCC 13.0.0 Status Report (2022-11-14), Stage 3 in effect now 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
2022-11-15 15:47           ` Martin Liška [this message]
2023-04-26 13:51             ` libsanitizer: sync from master 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=02a9e4ef-4d83-e4c4-cfeb-5e94fe63f1b3@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).