From: dewar@gnat.com
To: carlo@alinoe.com, fp@fpx.de
Cc: gcc@gcc.gnu.org
Subject: Re: Buffer Overflow Attacks
Date: Sun, 14 Oct 2001 08:01:00 -0000 [thread overview]
Message-ID: <20011014150103.2A3CDF28C0@nile.gnat.com> (raw)
<<Because of this, complete new languages have been designed (Java and C#),
which - as a result of that - are considerably slower. I don't think that
>>
This is misleading, Ada has shown for a long time that bounds checking need
not be that expensive. The performance of Java is not substantially due to
this feature at all. The obvious approach in a compiler to prevent this
kind of error is to generate appropriate runtime checks, and it is by
no means impossible to do this kind of code generation for C (indeed
it can be done already by some C translators). Yes there is overhead, but
probably not significantly more than would occur for the schemes discussed
here (e.g. separated data and control stacks).
next reply other threads:[~2001-10-14 8:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-14 8:01 dewar [this message]
2001-10-14 10:25 ` Florian Weimer
2001-10-14 11:08 ` Joseph S. Myers
2001-10-14 12:14 ` Florian Weimer
2001-10-14 12:29 ` Joseph S. Myers
2001-10-18 15:02 ` Michael Eager
-- strict thread matches above, loose matches on Subject: below --
2001-10-31 16:39 mike stump
2001-10-18 17:00 mike stump
2001-10-31 10:01 ` Florian Weimer
2001-10-14 12:25 dewar
2001-10-14 5:32 Frank Pilhofer
2001-10-14 7:33 ` Carlo Wood
2001-10-14 10:50 ` Florian Weimer
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=20011014150103.2A3CDF28C0@nile.gnat.com \
--to=dewar@gnat.com \
--cc=carlo@alinoe.com \
--cc=fp@fpx.de \
--cc=gcc@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).