search for: hoking

Displaying 5 results from an estimated 5 matches for "hoking".

Did you mean: poking
2011 May 30
1
[LLVMdev] Type::removeAbstractTypeUser crash when freeing module from ExecutionEngine
hi list, I've got a situation where I'm constantly adding and removing Modules from an ExecutionEngine. When removing a module and the jitstate is freed, clean up of the StructLayoutMap ends up trying to access a Type instance was was already freed by the removal of another Module. In trying to debug this, it basically comes down to a Type instance serving as key in
2016 Mar 02
0
"Tick-counting" vs "Tick-less" timekeeping issues on VMs emulating BIOS PCs
...jiffies_t jiffies(void) { return (*(volatile uint32_t *)BIOS_timer); } typedef uint32_t mstime_t; typedef int32_t mstimediff_t; static inline mstime_t ms_timer(void) { return ((*(volatile uint32_t *)BIOS_timer) * 55); } lpxelinux.0 hangs while legacy works OK. I think we should not depend on hoking timer interrupts if we want to be compatible with virtual environments. Best, Patrick
2016 Mar 02
2
"Tick-counting" vs "Tick-less" timekeeping issues on VMs emulating BIOS PCs
On 03/01/16 21:11, H. Peter Anvin via Syslinux wrote: > On 03/01/16 07:21, Patrick Masotta via Syslinux wrote: >> >> At the moment I'm seeing timing issues on TFTP transfers (lwIP depends >> on the new interrupt based timer). I have consistently detected >> >> multiple Requests, double ACKs, etc. All these problems seem to be >> >> sourced on the
2000 Oct 05
2
attaching something.RData in pos=1
hi - running R 1.1.1 under LinuxPPC: i was pleasantly surprised to find that attaching .RData files was added somewhere along the line, but i am having trouble getting the sort of behavior that i got used to in S. specifically, i'd like to be able to attach() a file at pos=1 and edit its contents directly, then save() and detach() it. i know i can load() the file, but this merges its
2010 Oct 13
1
[LLVMdev] EXC_BAD_ACCESS: invalid MemoryBuffer from ContentCache::getBuffer
I'm using the latest llvm/clang 2.8 releases and am getting EXC_BAD_ACCESS crashes in ContentCache::getBuffer. This happens when I'm printing out errors from a compilation run and iterating over TextDiagnosticBuffer returned errors. When checking the errors, I construct a FullSourceLoc and do: int LineNum = SourceLoc.getInstantiationLineNumber(); int ColNum =