search for: big_array

...2004, Markus F.X.J. Oberhumer wrote: > On Thursday 16 December 2004 06:22, Chris Lattner wrote: >> On Thu, 16 Dec 2004, Markus F.X.J. Oberhumer wrote: >>> More problematic is the use of unsigned instead of size_t in many llvm >>> places - how does the the following file big_array.c compile on your >>> current 64-bit targets: >> >> Hrm, we definitely SUPPORT 64-bit targets, but I KNOW there are still some >> places where we probably do the wrong thing for huge sizes like this. >> >>> /* big_array.c */ >> >> This is not a...

...obably related to a varargs problem. > I still have to further investigate. Thanks, applied: http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20041213/022366.html > More problematic is the use of unsigned instead of size_t in many llvm places > - how does the the following file big_array.c compile on your current 64-bit > targets: Hrm, we definitely SUPPORT 64-bit targets, but I KNOW there are still some places where we probably do the wrong thing for huge sizes like this. > /* big_array.c */ This is not a good example, because it's a front-end test, but there ARE kno...