public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Maxim Ostapenko <m.ostapenko@partner.samsung.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	Kostya Serebryany <kcc@google.com>,
	       Dmitry Vyukov <dvyukov@google.com>,
	Marek Polacek <polacek@redhat.com>,
	       Yury Gribov <y.gribov@samsung.com>,
	       Slava Garbuzov <v.garbuzov@samsung.com>,
	       Vyacheslav Barinov <v.barinov@samsung.com>
Subject: Re: [PATCH 1/7] Libsanitizer merge from upstream r249633.
Date: Wed, 14 Oct 2015 07:54:00 -0000	[thread overview]
Message-ID: <20151014075410.GU478@tucnak.redhat.com> (raw)
In-Reply-To: <561D3749.8080501@partner.samsung.com>

On Tue, Oct 13, 2015 at 07:54:33PM +0300, Maxim Ostapenko wrote:
> On 13/10/15 14:15, Maxim Ostapenko wrote:
> >This is the raw merge itself. I'm bumping SONAME to libasan.so.3.
> >
> >-Maxim
> 
> I have just noticed that I've misused autoconf stuff (used wrong version).
> Here a fixed version of the same patch. Sorry for inconvenience.

Is libubsan, libtsan backwards compatible, or do we want to change SONAME
there too?

The aarch64 changes are terrible, not just because it doesn't yet have
runtime decision on what VA to use or that it doesn't support 48-bit VA,
but also that for the 42-bit VA it uses a different shadow offset from
39-bit VA.  But on the compiler side we have just one...
Though, only the 39-bit VA is enabled right now by default, so out of the
box the state is as bad as we had in 5.x - users wanting 42-bit VA or 48-bit
VA have to patch libsanitizer.

Have you verified libbacktrace sanitization still works properly (that is
something upstream does not test)?

Do you plan to update the asan tests we have to reflect the changes in
upstream?

	Jakub

  reply	other threads:[~2015-10-14  7:54 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-13 11:14 [PATCH 0/7] " Maxim Ostapenko
2015-10-13 11:16 ` [PATCH 2/7] " Maxim Ostapenko
2015-10-14  7:30   ` Jakub Jelinek
2015-10-15 10:34     ` Maxim Ostapenko
2015-10-19  7:28       ` Jakub Jelinek
2015-10-14  7:49   ` Yury Gribov
2015-10-13 11:18 ` [PATCH 3/7] " Maxim Ostapenko
2015-10-14  7:31   ` Jakub Jelinek
2015-10-13 11:18 ` [PATCH 4/7] " Maxim Ostapenko
2015-10-14  7:31   ` Jakub Jelinek
2015-10-13 11:20 ` [PATCH 5/7] " Maxim Ostapenko
2015-10-14  7:37   ` Jakub Jelinek
2015-10-14 16:23     ` Maxim Ostapenko
2015-10-13 11:21 ` [PATCH 6/7] " Maxim Ostapenko
2015-10-14  7:38   ` Jakub Jelinek
2015-10-13 11:22 ` [PATCH 7/7] " Maxim Ostapenko
2015-10-14  7:48   ` Jakub Jelinek
2015-10-14 10:52     ` Maxim Ostapenko
2015-10-14 11:06       ` Jakub Jelinek
2015-10-14 12:02         ` Maxim Ostapenko
2015-10-14 12:12           ` Jakub Jelinek
2015-10-16 11:34             ` Maxim Ostapenko
2015-10-19  7:22               ` Jakub Jelinek
     [not found] ` <561CE7BA.5070805@partner.samsung.com>
2015-10-13 16:54   ` [PATCH 1/7] " Maxim Ostapenko
2015-10-14  7:54     ` Jakub Jelinek [this message]
2015-10-14  9:34       ` Maxim Ostapenko
2015-10-14  9:46         ` Yury Gribov
2015-10-14 16:25         ` Maxim Ostapenko
2015-10-14 18:03       ` Adhemerval Zanella
2015-10-14 18:22         ` Evgenii Stepanov
2015-10-14 18:38           ` Renato Golin
2015-10-14 19:00             ` Andrew Pinski
2015-10-14 19:15               ` Renato Golin
2015-10-14 19:17                 ` Andrew Pinski
2015-10-15  7:55                   ` Ramana Radhakrishnan
2015-10-15  7:29                 ` Yury Gribov
2015-10-15  8:42                   ` Renato Golin
2015-10-15  9:21                     ` pinskia
2015-10-15  9:44                       ` Renato Golin
2015-10-16 13:50             ` Renato Golin
2015-10-16 14:06               ` Maxim Ostapenko
2015-10-16 14:12                 ` Renato Golin
2015-10-13 17:03 ` [PATCH 0/7] " 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=20151014075410.GU478@tucnak.redhat.com \
    --to=jakub@redhat.com \
    --cc=dvyukov@google.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=kcc@google.com \
    --cc=m.ostapenko@partner.samsung.com \
    --cc=polacek@redhat.com \
    --cc=v.barinov@samsung.com \
    --cc=v.garbuzov@samsung.com \
    --cc=y.gribov@samsung.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).