Displaying 3 results from an estimated 3 matches for "write_mem".
Did you mean:
write_me
2012 Nov 06
0
[LLVMdev] Bug in SelectionDAG visitTargetIntrinsic
void SelectionDAGBuilder::visitTargetIntrinsic(const CallInst &I,
- unsigned Intrinsic) {
- bool HasChain = !I.doesNotAccessMemory();
- bool OnlyLoad = HasChain && I.onlyReadsMemory();
+ unsigned Intrinsic) {
+ // Info is set by getTgtMemInstrinsic
+ TargetLowering::IntrinsicInfo Info;
+ bool
2012 Nov 06
4
[LLVMdev] FW: Bug in SelectionDAG visitTargetIntrinsic
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
2007 Mar 05
0
[PATCH 3/10] linux 2.6.18: constify instances of ''struct file_operations''
.../char/mem.c 2007-02-27 16:27:37.000000000 +0100
@@ -194,7 +194,7 @@ static int open_mem(struct inode * inode
return capable(CAP_SYS_RAWIO) ? 0 : -EPERM;
}
-struct file_operations mem_fops = {
+const struct file_operations mem_fops = {
.llseek = memory_lseek,
.read = read_mem,
.write = write_mem,
Index: head-2007-02-27/drivers/xen/evtchn/evtchn.c
===================================================================
--- head-2007-02-27.orig/drivers/xen/evtchn/evtchn.c 2007-03-05 10:00:18.000000000 +0100
+++ head-2007-02-27/drivers/xen/evtchn/evtchn.c 2007-02-27 16:27:37.000000000 +0100
@@ -40...