From: Joseph Myers <joseph@codesourcery.com>
To: Ilya Enkovich <enkovich.gnu@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, MPX runtime 1/2] Integrate MPX runtime library
Date: Sat, 22 Nov 2014 00:26:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.10.1411212320400.32250@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20141119141555.GD47331@msticlxl57.ims.intel.com>
On Wed, 19 Nov 2014, Ilya Enkovich wrote:
> > If it's intended only as the latter - and this is documented - then you
> > don't have the libgcc-like requirements, and there's no point in having
> > multiple libraries. If it's intended for both, that points the way to
> > separate libraries (where the debugging-tool library would be used in that
> > use case, but the crash-reporter-interception case would expect programs
> > to have been linked with only the minimal library).
>
> Would it be enough to mention implicit link and resulting pthread
> dependency in -fcheck-pointer-bounds description in invoke.texi?
Well, that and say explicitly that it's intended as a debugging tool
rather than for general hardening.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2014-11-21 23:21 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 15:37 Ilya Enkovich
2014-11-11 18:09 ` Joseph Myers
2014-11-11 18:15 ` Joseph Myers
2014-11-11 20:26 ` Ilya Enkovich
2014-11-11 18:49 ` Andi Kleen
2014-11-11 20:22 ` H.J. Lu
2014-11-11 21:04 ` Andi Kleen
2014-11-11 21:11 ` H.J. Lu
2014-11-11 21:24 ` Andi Kleen
2014-11-11 21:37 ` Joseph Myers
2014-11-11 22:07 ` H.J. Lu
2014-11-11 22:10 ` Joseph Myers
2014-11-11 20:36 ` Joseph Myers
2014-11-12 16:20 ` Ilya Enkovich
2014-11-12 21:41 ` Joseph Myers
2014-11-12 22:56 ` Ilya Enkovich
2014-11-12 23:11 ` Joseph Myers
2014-11-13 8:39 ` Ilya Enkovich
2014-11-13 20:56 ` Joseph Myers
2014-11-19 14:18 ` Ilya Enkovich
2014-11-19 18:05 ` Jeff Law
2014-11-19 18:16 ` Ilya Enkovich
2014-11-21 16:04 ` Ilya Enkovich
2014-11-21 23:49 ` Joseph Myers
2014-11-24 14:28 ` Ilya Enkovich
2014-12-09 8:25 ` Ilya Enkovich
2014-12-09 20:48 ` Jeff Law
2014-12-09 20:56 ` Ilya Enkovich
2015-03-02 16:19 ` Ilya Enkovich
2015-03-04 17:36 ` Jeff Law
2014-11-22 0:26 ` Joseph Myers [this message]
2014-11-11 20:06 ` Jeff Law
2014-11-11 20:24 ` Ilya Enkovich
2014-11-12 20:53 ` Jeff Law
2014-11-12 8:36 ` Richard Biener
2014-11-12 8:38 ` Jakub Jelinek
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=alpine.DEB.2.10.1411212320400.32250@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=andi@firstfloor.org \
--cc=enkovich.gnu@gmail.com \
--cc=gcc-patches@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).