--- Comment #7 from tege-gcc at swox dot com 2008-02-21 22:01 ---
Sorry, but you ought to read and understand what I write before
you comment, otherwise it becomes rather pointless.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35271
--- Comment #6 from pinskia at gcc dot gnu dot org 2008-02-21 15:53 ---
> int variable;
This variable does not have be aligned 16byte.
> long long ebi, windowsize, last_windowsize;
Or even these.
The first one is word aligned. The second one just has to be 8 byte aligned.
--
--- Comment #5 from tege-gcc at swox dot com 2008-02-21 14:01 ---
The attachment is not the right file.
I tried to "edit" it but I cannot find out how to do it.
The proper test case is in the comment before this one.
Sorry, I am bugzilla challenged.
--
http://gcc.gnu.org/bugzilla/sh
--- Comment #4 from tege-gcc at swox dot com 2008-02-21 13:57 ---
(From update of attachment 15196)
#include
long align;
foo (int flag)
{
int variable;
if (flag == 0)
return (((long)&variable ^ align) & 0xf);
align = (long)&variable;
foo (flag - 1);
}
main ()
{
if (foo
--- Comment #3 from tege-gcc at swox dot com 2008-02-21 13:53 ---
Testcase? Because we do align it for both x86_64-* and i386-darwin.
Well, not as mandated in the 64-bit ABI.
Now the SVSV i386 ABI says it should be aligned at 4 (word)
bytes boundary.
This is hardly
--- Comment #2 from tege-gcc at swox dot com 2008-02-21 13:49 ---
Created an attachment (id=15196)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15196&action=view)
Alignment test
This is not a strictly correct test case, it may fail even if
the compiler aligns the stack properly,
--- Comment #1 from pinskia at gcc dot gnu dot org 2008-02-20 23:10 ---
Testcase? Because we do align it for both x86_64-* and i386-darwin.
Now the SVSV i386 ABI says it should be aligned at 4 (word) bytes boundary.
--
pinskia at gcc dot gnu dot org changed:
What|Re
