On Tue, 7 Dec 1999, Richard Henderson wrote:
>You probably want to rename those somehow. I don't know
>about you but I find 2_ and 4_ prefixes unintelligable.
Agreed, that is why I am wondering about it. I had not more fantasy when I
gone to implement it ;).
>Perhaps __struct_cacheline_aligned? I don't really like
>it but it's at least descriptiveof how it might be used
>differently from the previous x86 macro...
go for __struct_cacheline_aligned, thx.
>> I am also not 100% sure if
>> __gcc_cacheline_aligned works fine with gcc-2.7.2.3 or not.
>
>Does it give a warning? If so it doesn't work, if not it does.
I dropped all the gcc from my machines as I have all recent installs of
the distribution. Does somebody has a gcc-2.7.2.3 installed out there (so
I won't have to recompile?)? If so can you try to compile this piece of
code and see if gcc report errors. also please run `gcc -S test.c` and
show us the generated test.s.
I am not very concerned about warnings because if somebody want to go fast
he probably uses a recent gcc (do you agree?). Having such structures not
aligned won't harm anything but performances.
main()
{
int p __attribute__((__aligned__(32)));
}
Andrea
