Displaying 5 results from an estimated 5 matches for "wisked".
Did you mean:
risked
2006 Oct 19
0
AIX 5.2 Samba 3.0.23c Samba peculiarities
Hi All,
After successfully installing the AIX Binaries (Thanks Bill), and manageing
to join as a ADS Domain Member I have a couple of peculiarities of which I
need to get to the bottom.
Problem A
When connecting to a share, I can connect OK , and get authenticated OK, I
can create files in the share and open files in the share, but cannot list
files in the share or delete files I have created.
2012 Oct 16
1
Building a package with an existing dll
I have setup a package directory structure with all the relevent files in the
src, R, man and data directories.
Also have the correct DESCRIPTION and NAMESPACE files in the root directory.
I don't wisk to recompile the .dll file in the src directory as it currently
works fine if I locate it in the same workdirectory as my R source code that
calls it.
This is a little tedious having to move
2013 Aug 19
3
[LLVMdev] Issue with X86FrameLowering __chkstk on Windows 8 64-bit / Visual Studio 2012
Hi,
I'm using LLVM to convert expressions to native assembly, the problem
is when LLVM compiles this code:
define void @fn_0000000000000000(i8*, i8*, i8*) {
bb:
%res = alloca i32
%3 = load i32* %res
%4 = bitcast i8* %0 to i32*
%5 = load i32* %4
%6 = bitcast i8* %0 to i32*
%7 = load i32* %6
%8 = xor i32 %5, %7
store volatile i32 %8, i32* %res
%9 = load i32* %res
%10 = icmp
2011 Jul 29
2
special recursive filter
Hi,
I have a question about a special recursive filter problem.
What I have:
- given variables:
x: time series with rather randomly occuring '0' and '1'
wait: non negative integer
- a working but ineffectiv implementation (see below)
How the implementation works (what I want):
The filter should drill holes of distance 'wait' between the '1' in x, e.g.
x =
2013 Aug 27
0
[LLVMdev] Issue with X86FrameLowering __chkstk on Windows 8 64-bit / Visual Studio 2012
It's not a solution to the actual bug (which is, as the thread you linked
discusses, a problem with the assumption on LLVM's part that the __chkstk
function lies within 2GB of the emitted code's address space) but there is
a simple workaround: hoist all allocas to the first basic block of your
function. This allows the JIT to perform all stack allocations in a single
adjustment of the