Re: (no) strict aliasing

[Thomas Bushnell BSG]

Marcus Brinkmann <address@hidden> writes:

> The only way I found to make allocators like ports_create_port to
> reliably work without disabling aliasing alltogether would be to have
> the function return void * and use the __malloc__ function attribute.

Shouldn't the __malloc__ attribute work, even if you don't return a
type like void *?

> I am hitting similar problems in the code I write for the L4 port.  I
> was wondering what you think about it -- if we should disable strict
> aliasing globally, or fix such code individually.

In my opinion, we should demand a GCC feature that allows us to
disable it on a per-function basis.

Thomas