From: Ulrich Drepper <drepper@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: propolice support for linux
Date: Thu, 13 Jan 2005 23:06:05 -0800 [thread overview]
Message-ID: <a36005b505011323061bd2e4a9@mail.gmail.com> (raw)
In-Reply-To: <20050113225244.GH14127@boetes.org>
On Thu, 13 Jan 2005 23:52:22 +0100, Han Boetes <han@mijncomputer.nl> wrote:
> To avoid that I would like to ask you if you can show me some
> example-code, something I which can compile and run and see for
> myself, for the following situations:
The analysis of the patch does not stem from trying programs and
seeing them failing. The gcc maintainers looked at it with
understanding of the compiler and the way the patch interacts with the
existing code. It might be possible for them to come up with a
program which is miscompiled. More importantly, though, it'll most
probably be possible to come up with code which should be instrumented
but isn't. You must agree that this is a terrible thing to happen.
The patch gives a wrong sense of security.
Finally, the gcc patch is not going to work as is on architectures
like IA-64 which do not have the kind of adressing modes which are
needed for the code to work.
To fully understand the problem, you need to understand compiler
design, and especially RTL. The latter by itself is another problem:
getting the code work in gcc 4 is at least challenging due the SSA.
Anyway, if you want more information you'll need to ask the gcc people.
next prev parent reply other threads:[~2005-01-14 7:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 13:46 propolice support for linux Han Boetes
2005-01-13 14:04 ` Christoph Hellwig
2005-01-13 14:53 ` Arjan van de Ven
2005-01-13 16:37 ` Han Boetes
2005-01-13 17:02 ` Arjan van de Ven
2005-01-13 19:32 ` Han Boetes
2005-01-14 7:35 ` Arjan van de Ven
2005-01-13 17:07 ` Bill Davidsen
2005-01-13 17:31 ` Han Boetes
2005-01-13 17:58 ` Zwane Mwaikambo
2005-01-13 18:17 ` Han Boetes
2005-01-14 4:25 ` Mitchell Blank Jr
2005-01-14 10:30 ` Han Boetes
2005-01-15 2:25 ` Mitchell Blank Jr
2005-01-15 8:10 ` Han Boetes
2005-01-13 14:07 ` Arjan van de Ven
2005-01-13 14:15 ` Jakub Jelinek
2005-01-13 19:58 ` Andi Kleen
2005-01-13 21:11 ` Ulrich Drepper
2005-01-13 22:52 ` Han Boetes
2005-01-14 6:25 ` Willy Tarreau
2005-01-14 7:06 ` Ulrich Drepper [this message]
2005-01-14 14:08 ` Nix
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=a36005b505011323061bd2e4a9@mail.gmail.com \
--to=drepper@gmail.com \
--cc=linux-kernel@vger.kernel.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