From: Maxim Ostapenko <m.ostapenko@partner.samsung.com>
To: Jakub Jelinek <jakub@redhat.com>,
Kostya Serebryany <kcc@google.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Cc: 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: [PATCH v2 0/6] Libsanitizer merge from upstream r250806 (was r249633).
Date: Tue, 20 Oct 2015 11:17:00 -0000 [thread overview]
Message-ID: <56262292.3030803@partner.samsung.com> (raw)
Hi,
this is the second attempt to perform libsanitizer merge from upstream.
In previous patch set (
https://gcc.gnu.org/ml/gcc-patches/2015-10/msg01212.html) we have
revealed an issue with heuristic for old/new style ubsan_data that was
needed to be fixed upstream + some errors in compiler changes were
found. I thought that it would me too messy to proceed review in the
previous thread, so creating the new one.
The first patch is the merge itself. Since the heuristic fix for old/new
style ubsan_data selection was applied upstream, I'm bumping revision to
r250806.
Since there aren't significant changes from r249633, I think this should
be fine.
The second one combines all compiler-related changes and addresses
Jakub's nits from previous review.
Patches 3, 4 and 5 are applied to library and were preapproved in
previous review, but I'm attaching them here to form the full patch set.
In patch 6, I'm trying to add a brief instruction how to perform the
merge. This is just a documentation patch.
Tested and {A, UB}San bootstrapped on x86-linux-gnu, x86_64-linux-gnu
and aarch64-linux-gnu targets.
Thanks,
-Maxim
next reply other threads:[~2015-10-20 11:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 11:17 Maxim Ostapenko [this message]
2015-10-20 11:20 ` [PATCH v2 1/6] " Maxim Ostapenko
2015-10-20 11:56 ` Jakub Jelinek
2015-10-20 14:14 ` Maxim Ostapenko
2015-10-20 11:22 ` [PATCH v2 2/6] " Maxim Ostapenko
2015-10-20 12:02 ` Jakub Jelinek
2015-10-20 11:25 ` [PATCH v2 0/6] " Maxim Ostapenko
2015-10-20 11:28 ` [PATCH v2 4/6] " Maxim Ostapenko
2015-10-20 11:30 ` [PATCH v2 5/6] " Maxim Ostapenko
2015-10-20 11:45 ` [PATCH v2 6/6] " Maxim Ostapenko
2015-10-20 12:06 ` Jakub Jelinek
2015-10-21 9:19 ` Yury Gribov
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=56262292.3030803@partner.samsung.com \
--to=m.ostapenko@partner.samsung.com \
--cc=dvyukov@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=kcc@google.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).