public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ygribov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/64839] libsanitizer shouldn't require <rpc/xdr.h>
Date: Tue, 12 May 2015 07:02:00 -0000 [thread overview]
Message-ID: <bug-64839-4-FYknuZZDeR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64839-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64839
--- Comment #13 from ygribov at gcc dot gnu.org ---
Author: ygribov
Date: Tue May 12 07:02:09 2015
New Revision: 223032
URL: https://gcc.gnu.org/viewcvs?rev=223032&root=gcc&view=rev
Log:
2015-05-12 Yury Gribov <y.gribov@samsung.com>
Backport from mainline
2015-04-13 Yury Gribov <y.gribov@samsung.com>
PR sanitizer/64839
* sanitizer_common/sanitizer_platform.h: Cherry pick
upstream r234470.
* sanitizer_common/sanitizer_platform_limits_posix.cc: Ditto.
* configure.ac (RPC_DEFS): Check for precense of RPC headers.
* sanitizer_common/Makefile.am (DEFS): Pass info to compiler.
* Makefile.in: Regenerate.
* asan/Makefile.in: Regenerate.
* config.h.in: Regenerate.
* configure: Regenerate.
* interception/Makefile.in: Regenerate.
* libbacktrace/Makefile.in: Regenerate.
* lsan/Makefile.in: Regenerate.
* sanitizer_common/Makefile.in: Regenerate.
* tsan/Makefile.in: Regenerate.
* ubsan/Makefile.in: Regenerate.
Modified:
branches/gcc-5-branch/libsanitizer/ChangeLog
branches/gcc-5-branch/libsanitizer/Makefile.in
branches/gcc-5-branch/libsanitizer/asan/Makefile.in
branches/gcc-5-branch/libsanitizer/config.h.in
branches/gcc-5-branch/libsanitizer/configure
branches/gcc-5-branch/libsanitizer/configure.ac
branches/gcc-5-branch/libsanitizer/interception/Makefile.in
branches/gcc-5-branch/libsanitizer/libbacktrace/Makefile.in
branches/gcc-5-branch/libsanitizer/lsan/Makefile.in
branches/gcc-5-branch/libsanitizer/sanitizer_common/Makefile.am
branches/gcc-5-branch/libsanitizer/sanitizer_common/Makefile.in
branches/gcc-5-branch/libsanitizer/sanitizer_common/sanitizer_platform.h
branches/gcc-5-branch/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc
branches/gcc-5-branch/libsanitizer/tsan/Makefile.in
branches/gcc-5-branch/libsanitizer/ubsan/Makefile.in
next prev parent reply other threads:[~2015-05-12 7:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 14:50 [Bug sanitizer/64839] New: " harald at gigawatt dot nl
2015-01-29 14:49 ` [Bug sanitizer/64839] " harald at gigawatt dot nl
2015-02-10 6:54 ` pinskia at gcc dot gnu.org
2015-03-30 15:41 ` y.gribov at samsung dot com
2015-04-09 8:14 ` y.gribov at samsung dot com
2015-04-10 7:53 ` y.gribov at samsung dot com
2015-04-10 8:04 ` jakub at gcc dot gnu.org
2015-04-13 9:00 ` ygribov at gcc dot gnu.org
2015-04-13 10:23 ` jakub at gcc dot gnu.org
2015-05-07 13:04 ` thierry.reding at gmail dot com
2015-05-09 5:46 ` y.gribov at samsung dot com
2015-05-09 8:36 ` harald at gigawatt dot nl
2015-05-09 8:39 ` y.gribov at samsung dot com
2015-05-12 7:02 ` ygribov at gcc dot gnu.org [this message]
2015-05-12 10:42 ` thierry.reding at gmail dot com
2015-05-12 10:44 ` y.gribov at samsung dot com
2015-05-12 11:09 ` geoff at geoff dot codes
2015-05-12 11:31 ` y.gribov at samsung dot com
2015-05-12 11:57 ` geoff at geoff dot codes
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=bug-64839-4-FYknuZZDeR@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).