Hi, In PromoteIntOp_STORE, why can we not promote a value and generate a truncating store if the incoming store is a truncating store? Naively, I can't see why we can promote the incoming value to a legal type and then generate a truncating store. For example, one has incoming code that produces an i16 via some operation and does a truncating store the result of that value in i8. If that operation only has a 32 bit variant, it seems reasonable to promote the i16 to i32 and replace the truncating store from i16 to i8 with one from i32 to i8. Thanks, -- Mon Ping
Hi Mon Ping,> In PromoteIntOp_STORE, why can we not promote a value and generate a > truncating store if the incoming store is a truncating store?as far as I can see you can just remove the assertion. Ciao, Duncan.
Hi Duncan, Thanks! I'll do so. -- Mon Ping On Dec 13, 2008, at 8:19 AM, Duncan Sands wrote:> Hi Mon Ping, > >> In PromoteIntOp_STORE, why can we not promote a value and generate a >> truncating store if the incoming store is a truncating store? > > as far as I can see you can just remove the assertion. > > Ciao, > > Duncan. > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
Possibly Parallel Threads
- [LLVMdev] LegalizeIntegerType and truncating stores
- [LLVMdev] legalization of truncating stores in LegalizeDAG.cpp
- [LLVMdev] legalization of truncating stores in LegalizeDAG.cpp
- What should a truncating store do?
- [LLVMdev] 32bit pointers on a (pure) 64bit architecture