Re: relearning C: why does an in-place change to a char* segfault?

Lawrence D'Oliveiro <ldo@nz.invalid> writes:

On Sat, 03 Aug 2024 17:07:37 -0700, Keith Thompson wrote:
>

... general compression isn't something I've seen ...

>
I recall Apple had a patent on some aspects of the “PEF” executable format
that they created for their PowerPC machines running old MacOS. This had
to do with some clever instruction encodings for loading stuff into
memory.

Is that relevant to what I asked about?

What I had in mind is something that, given this:

    static int buf = { 1, 1, 1, ..., 1 }; // say, 1000 elements

would store something less than 1000*sizeof(int) bytes in the executable
file.  I wouldn't be hard to do, but I'm not convinced it would be
worthwhile.

--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
void Void(void) { Void(); } /* The recursive call of the void */