public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "y.gribov at samsung dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/64839] libsanitizer shouldn't require <rpc/xdr.h> Date: Mon, 30 Mar 2015 15:41:00 -0000 [thread overview] Message-ID: <bug-64839-4-WjmrwKNftZ@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 Yury Gribov <y.gribov at samsung dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |y.gribov at samsung dot com --- Comment #3 from Yury Gribov <y.gribov at samsung dot com> --- I've sent fix upstream: http://reviews.llvm.org/D8698 . We'll probably need similar checks for existance of xdr.h in GCC Autoconf.
next prev parent reply other threads:[~2015-03-30 14:01 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 [this message] 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 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-WjmrwKNftZ@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: linkBe 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).