Displaying 3 results from an estimated 3 matches for "emitaggregatezero".
2007 Nov 07
0
[LLVMdev] RFC: llvm-convert.cpp Patch
...how CopyAggregate and ZeroAggregate handle alignment (problem points
marked with "QQ"). Also, I noticed potential problems with how we
handle call arguments and return results (what if they are strangely
aligned/volatile?), marked with FIXME.
While there, I fixed the following:
- Taught EmitAggregateZero not to do element by element zeroing
if the LLVM type doesn't cover the gcc type. Also, not to do
it if there are too many aggregate elements.
- Added a bunch of missing alignment/volatile stuff on various
loads and stores.
- Fixed up a lot of bogus handling of volatility in the complex
number...
2007 Nov 07
3
[LLVMdev] RFC: llvm-convert.cpp Patch
How about this patch then?
-bw
Index: gcc/llvm-convert.cpp
===================================================================
--- gcc/llvm-convert.cpp (revision 43658)
+++ gcc/llvm-convert.cpp (working copy)
@@ -758,7 +758,7 @@
}
-Value *TreeToLLVM::Emit(tree exp, Value *DestLoc) {
+Value *TreeToLLVM::Emit(tree exp, Value *DestLoc, unsigned Alignment) {
2007 Nov 07
2
[LLVMdev] RFC: llvm-convert.cpp Patch
...regate handle alignment (problem points
> marked with "QQ"). Also, I noticed potential problems with how we
> handle call arguments and return results (what if they are strangely
> aligned/volatile?), marked with FIXME.
>
> While there, I fixed the following:
> - Taught EmitAggregateZero not to do element by element zeroing
> if the LLVM type doesn't cover the gcc type. Also, not to do
> it if there are too many aggregate elements.
> - Added a bunch of missing alignment/volatile stuff on various
> loads and stores.
> - Fixed up a lot of bogus handling of volatil...