Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > sci.math > #647128

Johnny Depp prevention [Windows 11 etc...] (Re: Homework: Game Engine in WebGPU)

From Mild Shock <janburse@fastmail.fm>
Newsgroups sci.physics.relativity, sci.math
Subject Johnny Depp prevention [Windows 11 etc...] (Re: Homework: Game Engine in WebGPU)
Date 2026-08-03 18:18 +0200
Message-ID <114qf1i$t244$3@solani.org> (permalink)
References (15 earlier) <11475ju$fsrh$1@solani.org> <0jWdnUSmIegmh_r3nZ2dnZfqnPSdnZ2d@giganews.com> <11478gh$fv28$4@solani.org> <11478t5$fvic$1@solani.org> <114olvc$s9h3$1@solani.org>

Cross-posted to 2 groups.

Show all headers | View raw


Hi,

 > I've also added comp.theory so Mild Shock can comment.

 > that has different
 > *  sizeof ( void * ), and
 > *  sizeof ( void (*)( void ) ),

Could indicate a data RAM and code ROM model.
Which has then the advantage of:

Modern operating systems like Windows 11
enforce strict Data Execution Prevention (DEP)
(or NX/XD bit security features) to prevent
malicious programs from injecting and executing
code inside data-only memory regions.
https://root-nation.com/en/soft-en/lifehacks/en-dep-windows-all-about/

I adopted data RAM and code ROM model for
pi-WAM from Hack, which has the same separation:

Slide 58, Hack Computer
https://drive.google.com/file/d/1Z_fxYmmRNXTkAzmZ6YMoX9NXZIRVCKiw/view

But my motivation was not Johnny Depp prevention.
Rather the caching of GPUs. Because WGSL
allows storage annotations read_write and

read. I use read_write for the data RAM
of my Hack VM variant, and read for the
code ROM of my Hack VM variant. You can

see that here, its open source:

@group(0) @binding(0) var<storage, read> code: array<i32>;
@group(0) @binding(1) var<storage, read_write> state: array<i32>;

11.4 Giga Lips with a Budget Laptop
https://github.com/Jean-Luc-Picard-2021/gigabudget

Hope this Helps!

Bye

Johann 'Myrkraverk' Oskarsson schrieb:
 > On 03/08/2026 6:28 PM, David Brown wrote:
 >> On 03/08/2026 11:41, Richard Harnden wrote:
 >>> On 03/08/2026 09:16, David Brown wrote:
 >>
 >>>> On most targets, function pointers are the same size as void* 
pointers. But there are exceptions, with some small microcontrollers and 
DSPs having different kinds of pointers with different sizes, depending 
on the memory space involved.  I have yet to see a situation where there 
was any reason for storing a function address in a "void*" rather than a 
more appropriate typedef, such as :
 >>>>
 >>>>      typedef void (*FVoid)(void);
 >>>
 >>> dlsym requires that pointer-to-function is compatible with a void*
 >>>
 >>
 >> As I say, I have yet to see a situation where using void* for 
function pointers was more appropriate than using a function pointer 
type.  If the OS system calls or standard OS libraries makes it a 
requirement that function pointers are converted to or from void* for 
some calls, then of course you need to follow those requirements - it's 
the people who designed the interfaces that made questionable design 
choices.
 >>
 >
 > Nope, you're wrong.  You're dead wrong.  The world isn't built on C,
 > even though here in comp.lang.c we like to pretend it is.
 >
 > Several language environments allow function generation on the fly,
 > these functions need to be garbage collected.  Common Lisp is an
 > example, therefore comp.lang.lisp is added to this discussion.
 >
 > I've also added comp.theory so Mild Shock can comment.
 >
 > You will have to go out of your way to make a computer architecture
 > incompatible with garbage collected and heap allocated binary code,
 > something I've been told SBCL does internally [1] to create an archi-
 > tecture that has different
 >
 > *  sizeof ( void * ), and
 > *  sizeof ( void (*)( void ) ),
 >
 > and when you do that, I'll just claim you're making a /malicious
 > computer architecture/ and refuse to use it.
 >
 >
 > [1] I've not looked at the code, but told the garbage collector can
 > and will at least move the code around, if not collect it.

Back to sci.math | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Homework: Game Engine in WebGPU (Was: Train yourself to become a nosomatic AI chirurgeon) Mild Shock <janburse@fastmail.fm> - 2026-08-03 02:05 +0200
  Re: Homework: Game Engine in WebGPU (Was: Train yourself to become a nosomatic AI chirurgeon) Piotr Agamirov <ppp@togit.ru> - 2026-08-03 12:05 +0000
  Johnny Depp prevention [Windows 11 etc...] (Re: Homework: Game Engine in WebGPU) Mild Shock <janburse@fastmail.fm> - 2026-08-03 18:18 +0200
    But how can you deploy, when its ROM? (Re: Johnny Depp prevention [Windows 11 etc...]) Mild Shock <janburse@fastmail.fm> - 2026-08-03 18:22 +0200
    Re: Johnny Depp prevention [Windows 11 etc...] (Re: Homework: Game Engine in WebGPU) Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-04 00:45 +0800
    Re: Johnny Depp prevention [Windows 11 etc...] (Re: Homework: Game Engine in WebGPU) Bayard Djabrailov <yjbob@aodorbv.ru> - 2026-08-03 17:28 +0000

csiph-web