Displaying 4 results from an estimated 4 matches for "constantfillarray".
2007 Aug 20
0
[LLVMdev] Problem with missing support for non-zero contant initializers.
...constant initializer. But D requires that (per
> default) static arrays are initialized with the default initializer
> for the element type. For float this happens to be NaN, so I cannot
> use a 'zeroinitializer'.
Wow, this *is* bad. I think the solution to this is to add a new
ConstantFillArray node. It would always have array type, would take a
single Constant* value, and would give you the filled array with that
constant. Please file a bug if you're interested.
-Chris
--
http://nondot.org/sabre/
http://llvm.org/
2007 Aug 20
1
[LLVMdev] Problem with missing support for non-zero contant initializers.
...D requires that (per
>> default) static arrays are initialized with the default initializer
>> for the element type. For float this happens to be NaN, so I cannot
>> use a 'zeroinitializer'.
>
> Wow, this *is* bad. I think the solution to this is to add a new
> ConstantFillArray node. It would always have array type, would take a
> single Constant* value, and would give you the filled array with that
> constant. Please file a bug if you're interested.
I believe this is already bug 1324.
Nick
2007 Aug 20
5
[LLVMdev] Problem with missing support for non-zero contant initializers.
Hi all.
I'm working on a LLVM based compiler for the D programming language by
Walter Bright.
D allows static arrays up to 16MB in size. I'm initializing global
static arrays with a constant initializer. But D requires that (per
default) static arrays are initialized with the default initializer
for the element type. For float this happens to be NaN, so I cannot
use a
2007 Aug 20
1
[LLVMdev] Problem with missing support for non-zero contant initializers.
...equires that (per
> > default) static arrays are initialized with the default initializer
> > for the element type. For float this happens to be NaN, so I cannot
> > use a 'zeroinitializer'.
>
> Wow, this *is* bad. I think the solution to this is to add a new
> ConstantFillArray node. It would always have array type, would take a
> single Constant* value, and would give you the filled array with that
> constant. Please file a bug if you're interested.
In Ada, global variables should in general be default initialized to undef
(not zero) so this could also be...