Re: [BDW-GC] Static cell/string/symbol allocation

2009-01-13 Thread Ken Raeburn
On Jan 12, 2009, at 19:04, Ludovic Courtès wrote: union { scm_t_cell cell[2]; double d_for_alignment; long long ll_for_alignment; } The issue with this is that there's nothing telling us how compilers should behave when encountering this. Even if the underlying hardware has a preferred

Re: [BDW-GC] Static cell/string/symbol allocation

2009-01-12 Thread Ludovic Courtès
Hi Ken, Thanks for your reply. Ken Raeburn raeb...@raeburn.org writes: There's no portable way, but it might be a bit more likely to happen if you try something like: union { scm_t_cell cell[2]; double d_for_alignment; long long ll_for_alignment; } The issue with this is that

Re: [BDW-GC] Static cell/string/symbol allocation

2009-01-12 Thread Ludovic Courtès
Hi! l...@gnu.org (Ludovic Courtès) writes: I modified snarf.h in the BDW-GC branch to transparently have all `SCM_SYMBOL ()' invocations use a statically allocated stringbuf. The symbol itself still has to be interned then so for simplicity the implementation statically allocates an