Displaying 3 results from an estimated 3 matches for "c34a5cc4".
2007 Nov 21
1
[LLVMdev] C embedded extensions and LLVM
...'m up in the air about
what a good separator would be. Simply whitespace?
i32$27*
i32 27*
i32(27)*
i32{27}*
i32 at 27*
--
Christopher Lamb
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20071120/c34a5cc4/attachment.html>
2007 Nov 11
0
[LLVMdev] C embedded extensions and LLVM
On Nov 10, 2007, at 11:07 PM, Christopher Lamb wrote:
> I've been playing around with clang/LLVM looking at adding partial
> support for the draft technical report for embedded C extensions
> (TR18037, http://www.open-std.org/jtc1/sc22/wg14/www/docs/
> n1169.pdf), specifically named address spaces.
>
> Named address spaces need to be tracked in LLVM in essentially all
2007 Nov 11
6
[LLVMdev] C embedded extensions and LLVM
I've been playing around with clang/LLVM looking at adding partial
support for the draft technical report for embedded C extensions
(TR18037, http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1169.pdf),
specifically named address spaces.
Named address spaces need to be tracked in LLVM in essentially all
the same places that alignment is tracked, which necessitates adding
the