Re: how to avoid a memset() optimization

"Jan C. =?iso-8859-1?Q?Vorbr=FCggen?=" <jvorbrueggen@mediasec.de>
13 Nov 2002 12:20:34 -0500

          From comp.compilers

Related articles
[4 earlier articles]
Re: how to avoid a memset() optimization christian.bau@freeserve.co.uk (Christian Bau) (2002-11-12)
Re: how to avoid a memset() optimization lars@bearnip.com (Lars Duening) (2002-11-12)
Re: how to avoid a memset() optimization cgweav@aol.com (Clayton Weaver) (2002-11-12)
Re: how to avoid a memset() optimization n2102139816.ch@chch.demon.co.uk (Charles Bryant) (2002-11-13)
Re: how to avoid a memset() optimization dobes@dobesland.com (Dobes Vandermeer) (2002-11-13)
Re: how to avoid a memset() optimization fjh@cs.mu.OZ.AU (Fergus Henderson) (2002-11-13)
Re: how to avoid a memset() optimization jvorbrueggen@mediasec.de (Jan C. =?iso-8859-1?Q?Vorbr=FCggen?=) (2002-11-13)
Re: how to avoid a memset() optimization usenet-1ugeabe@qeng-ho.org (Arthur Chance) (2002-11-13)
Re: how to avoid a memset() optimization cfc@shell01.TheWorld.com (Chris F Clark) (2002-11-15)
Re: how to avoid a memset() optimization usenet-1ugeabe@qeng-ho.org (Arthur Chance) (2002-11-15)
Re: how to avoid a memset() optimization joachim_d@gmx.de (Joachim Durchholz) (2002-11-17)
Re: how to avoid a memset() optimization cfc@shell01.TheWorld.com (Chris F Clark) (2002-11-20)
Re: how to avoid a memset() optimization thp@cs.ucr.edu (2002-11-24)
[1 later articles]
| List of all articles for this month |

From: "Jan C. =?iso-8859-1?Q?Vorbr=FCggen?=" <jvorbrueggen@mediasec.de>
Newsgroups: comp.compilers
Date: 13 Nov 2002 12:20:34 -0500
Organization: MediaSec Technologies GmbH
References: 02-11-030
Keywords: C, practice
Posted-Date: 13 Nov 2002 12:20:34 EST

Of course, there is also the difficulty in ensuring that a copy of the
data in question doesn't remain in backing store (e.g., a page file) because
on process rundown, the pages being deleted aren't written back but sent to
the free list right away. I'm sure of reading of some criminal investigations
yielding evidence by analysis of such files. (Windows is of course also famous
for leaving temporary files around almost indefinitely.)


Oh, and what about the copies in the OS's I/O buffers? or the memory of
attached I/O devices that were used to enter/read them?


This problem isn't easy to solve at all.


Jan


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.