On Sat, 01 Oct 2011, Bron Gondwana wrote:
> On Sat, Oct 01, 2011 at 02:03:32PM -0300, Henrique de Moraes Holschuh wrote:
> > On Sat, 01 Oct 2011, Bron Gondwana wrote:
> > > Do you see a case where the alignment of the "const char *" for
> > > value is significant?
> >
> > Yes, it is. How much dep
On Sat, Oct 01, 2011 at 02:03:32PM -0300, Henrique de Moraes Holschuh wrote:
> On Sat, 01 Oct 2011, Bron Gondwana wrote:
> > Do you see a case where the alignment of the "const char *" for
> > value is significant?
>
> Yes, it is. How much depends on the arch, some will just be slowed down in
> s
On Sat, 01 Oct 2011, Bron Gondwana wrote:
> Do you see a case where the alignment of the "const char *" for
> value is significant?
Yes, it is. How much depends on the arch, some will just be slowed down in
some specific cases (x86-64), others will actually bus-fault, so the
compiler will have to
Hi all,
I've been playing around with a file format for skiplist2. I've mostly
nailed down the details now, but I want an opinion:
Do you see a case where the alignment of the "const char *" for value is
significant?
The answer to this will determine the amount of padding required per reco
