🚀 go-pugleaf

In article <DKDA7D.Kw7@midway.uchicago.edu>, Michael Spertu writes:

> The standard says that the return value of malloc() should be properly
> aligned for all data type. On the one hand, code that uses floats will
> endure gross performance penalties if it doesn't check alignment, and
> programmers shouldn't have to align all their malloc()s. On the other
> hand, the code still runs, albeit inefficiently.

That is a quality-of-implementation issue and hence beyond the scope
of The Standard. All The Standard defines in the end is the output a C
program creates, not the timing nor (thanks to the as-if rule) the way
it creates it.

It should be relatively easy to write your own malloc() wrapper,
though, that calls malloc() for a slightly [1] larger block and
returns a better aligned pointer to within that block.

_______
[1] new_blocksize - old_blocksize, that is

-- __
__/// Arno Eigenwillig /\ <arno@yaps.rhein.de> \/  PGP key
\XX/   V+49-2225-5870  /\ <Arnooo @ #amigager> \/ available