From: Jakub Jelinek <jakub@redhat.com>
To: Yury Gribov <y.gribov@samsung.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
PHHargrove@lbl.gov, skunk@iskunk.org,
Viacheslav Garbuzov <v.garbuzov@samsung.com>
Subject: Re: [PATCH] Fix for PR57316 (avoid building sanitizer on old kernels)
Date: Thu, 23 Jan 2014 12:59:00 -0000 [thread overview]
Message-ID: <20140123125907.GH892@tucnak.redhat.com> (raw)
In-Reply-To: <52E10C18.2050504@samsung.com>
On Thu, Jan 23, 2014 at 04:33:28PM +0400, Yury Gribov wrote:
> Attached patch disables libsanitizer on older Linux distribs which
> lack necessary syscalls (see
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57316 for more details).
>
> Bootstrapped/regtested on x64.
>
> Ok to commit?
Ok, thanks, but:
> 2014-01-22 ygribov <ygribov@samsung.com>
Put your real name here instead.
> sanitizer/PR57316
PR sanitizer/57316
> * configure.ac: Check for missing syscalls.
> * Makefile.am: Likewise.
> * configure: Regenerate.
> * Makefile.in: Regenerate.
Jakub
next prev parent reply other threads:[~2014-01-23 12:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 12:33 Yury Gribov
2014-01-23 12:59 ` Jakub Jelinek [this message]
2014-01-23 14:33 ` 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=20140123125907.GH892@tucnak.redhat.com \
--to=jakub@redhat.com \
--cc=PHHargrove@lbl.gov \
--cc=gcc-patches@gcc.gnu.org \
--cc=skunk@iskunk.org \
--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).