Displaying 7 results from an estimated 7 matches for "m96bit".
2010 Nov 02
2
[LLVMdev] x86_fp80, f80, and -m96bit-long-double
Hi Duncan,
On Mon, 1 Nov 2010, Duncan Sands wrote:
> > Does llvm-gcc not intend to support -m96bit-long-double?
>
> Please open a bug report asking for support for -m96bit-long-double,
> to ensure this issue is not forgotten.
Given the thread that followed this post, I'm not sure whether you still
want a bug report. Is the plan to fix -m96bit-long-double or just remove
it and e...
2010 Nov 01
0
[LLVMdev] x86_fp80, f80, and -m96bit-long-double
...odifying that
> part of the frontend by finding a way to tell LLVM that 12 bytes are
> allocated for x86_fp80.
I think the "fact" that x86 long double is 16 byte aligned on x86-64 is
hard-wired in. I'm not sure how hard this would be to control via a
command line option (i.e. -m96bit-long-double).
> Looking inside test.ll, I see f80:128:128, but I also see sizeof(long
> double)*5 folded into 60. Changing f80:128:128 to f80:96:96 does not fix
> the errors reported by valgrind. If I instead fix the folded constant,
> the errors go away, of course.
If you had built...
2010 Nov 01
3
[LLVMdev] x86_fp80, f80, and -m96bit-long-double
...t;
#include <stdlib.h>
#define SIZE 5
int
main(void)
{
long double *a = malloc(sizeof(long double) * SIZE);
for (int i = 0; i < SIZE; ++i)
a[i] = i+1;
for (int i = 0; i < SIZE; ++i)
printf ("a[%d] = %Lf\n", i, a[i]);
free (a);
return 0;
}
% llvm-gcc -std=c99 -m96bit-long-double -emit-llvm -S -o test.ll test.c
% llvmc test.ll
% valgrind ./a.out |& grep Invalid
==3882== Invalid write of size 4
==3882== Invalid write of size 2
==3882== Invalid read of size 4
==3882== Invalid read of size 2
Looking inside test.ll, I see f80:128:128, but I also see sizeof(long...
2010 Nov 03
0
[LLVMdev] x86_fp80, f80, and -m96bit-long-double
Hi Joel,
>>> Does llvm-gcc not intend to support -m96bit-long-double?
>>
>> Please open a bug report asking for support for -m96bit-long-double,
>> to ensure this issue is not forgotten.
>
> Given the thread that followed this post, I'm not sure whether you still
> want a bug report. Is the plan to fix -m96bit-long-double...
2010 Nov 01
0
[LLVMdev] x86_fp80, f80, and -m96bit-long-double
...uot;fact" that x86 long double is 16 byte aligned on x86-64 is
>> hard-wired in.
>
> Note that it's not just about alignment, but mainly about the reserved storage size.
>
>> I'm not sure how hard this would be to control via a
>> command line option (i.e. -m96bit-long-double).
>
> Is there no different way to go about this? Our compiler currently supports the x87 long double type as
> a) 10 bytes, for Turbo Pascal and Delphi-compatibility
> b) 12 bytes, for non-Darwin ABI/C x86 compatibility
> c) 16 bytes, for Darwin x86 ABI/C and x86_64 ABI...
2010 Nov 01
4
[LLVMdev] x86_fp80, f80, and -m96bit-long-double
...wrote:
> I think the "fact" that x86 long double is 16 byte aligned on x86-64 is
> hard-wired in.
Note that it's not just about alignment, but mainly about the reserved storage size.
> I'm not sure how hard this would be to control via a
> command line option (i.e. -m96bit-long-double).
Is there no different way to go about this? Our compiler currently supports the x87 long double type as
a) 10 bytes, for Turbo Pascal and Delphi-compatibility
b) 12 bytes, for non-Darwin ABI/C x86 compatibility
c) 16 bytes, for Darwin x86 ABI/C and x86_64 ABI/C compatibility
long do...
2010 Nov 02
0
[LLVMdev] x86_fp80, f80, and -m96bit-long-double
...e reserved storage size.
actually it is about the alignment, since the reserved storage size is (in LLVM)
the number of bytes needed to store the type (i.e. 10 bytes) rounded up by the
alignment.
>> I'm not sure how hard this would be to control via a
>> command line option (i.e. -m96bit-long-double).
>
> Is there no different way to go about this? Our compiler currently supports the x87 long double type as
> a) 10 bytes, for Turbo Pascal and Delphi-compatibility
I doubt 10 bytes is supportable in LLVM without some surgery. Consider an
array of long double,
long doubl...