search for: writemem

...39;s pointing at has in fact been deallocated by the intrinsic, so the uses of it through the variable tmp4 are wrong. Maybe some dependencies between alloca and the stackrestore instrinsic are missing or how should this work? In Intrinsics.td it says // Note: we treat stacksave/stackrestore as writemem because we don't otherwise // model their dependencies on allocas. def int_stacksave : Intrinsic<[llvm_ptr_ty]>, GCCBuiltin<"__builtin_stack_save">; def int_stackrestore : Intrinsic<[], [llvm_ptr_ty]>, GCCBuilt...

Hi Team, I'm working on a new pure functional language and I'm trying to add GC support for that. Because all vars are immutable, the IR that my frontend generates are all register based, i.e. no alloca, and no readmem, writemem unless accessing/constructing structs. If I use the traditional GC with gcroot intrinsic, it will need to emit more code for liveness tracking, storing the IR values into the gcroot, which seems convoluted. I found using stack map / statepoints very plausible here, because it only needs all live...

Is there a reason that we don't have a definition for write-only intrinsics? Specifically, utils/TableGen/CodeGenIntrinsics.h contains: // Memory mod/ref behavior of this intrinsic. enum { NoMem, ReadArgMem, ReadMem, ReadWriteArgMem, ReadWriteMem } ModRef; The problem with this seems to be that "store" instructions, like the PPC STVX instruction, that are primarily defined by an intrinsic (int_ppc_altivec_stvx for the STVX instruction) get tagged as "mayLoad" even though they don't load anything. This is because...

From: Villmow, Micah Sent: Tuesday, November 06, 2012 1:37 PM To: 'llvm-dev at cs.uiuc.edu' Cc: Guo, Xiaoyi Subject: Bug in SelectionDAG visitTargetIntrinsic We ran into a problem where specifying IntrNoMem was causing our instruction selection to fail with target specific intrinsics. After looking into the code and ISel debug it looks like tablegen and SelectionDAG are using different

...= HasChain && I.onlyReadsMemory(); + unsigned Intrinsic) { + // Info is set by getTgtMemInstrinsic + TargetLowering::IntrinsicInfo Info; + bool IsTgtIntrinsic = TLI.getTgtMemIntrinsic(Info, I, Intrinsic); + bool HasChain = Info.readMem || Info.writeMem; + bool OnlyLoad = HasChain && Info.readMem; This doesn't seem right. If a call is marked ReadNone, it doesn't seem legal to select it to an intrinsic that read / write memory. By definition a "ReadNone" function cannot touch memory, no? Evan On Nov 6, 2012, at 1:45 P...

...29 PM, Chuan Qiu via llvm-dev wrote: > > Hi Team, > I'm working on a new pure functional language and I'm trying to add GC > support for that. > > Because all vars are immutable, the IR that my frontend generates are all > register based, i.e. no alloca, and no readmem, writemem unless > accessing/constructing structs. > > If I use the traditional GC with gcroot intrinsic, it will need to emit > more code for liveness tracking, storing the IR values into the gcroot, > which seems convoluted. > > I found using stack map / statepoints very plausible here...

...allocated by the > intrinsic, so the uses of it through the variable tmp4 are wrong. > > Maybe some dependencies between alloca and the stackrestore instrinsic > are missing or how should this work? > > In Intrinsics.td it says > > // Note: we treat stacksave/stackrestore as writemem because we don't > otherwise > // model their dependencies on allocas. > def int_stacksave : Intrinsic<[llvm_ptr_ty]>, > GCCBuiltin<"__builtin_stack_save">; > def int_stackrestore : Intrinsic<[], [llvm_ptr_ty]>, >...

...here a reason that we don't have a definition for write-only > intrinsics? Specifically, utils/TableGen/CodeGenIntrinsics.h contains: I don't think so, I'm not opposed to it. > If there is no particular reason for the current behavior, then I'll > propose a patch to add a WriteMem tag for intrinsics. Great, thanks! -Chris