Displaying 6 results from an estimated 6 matches for "preati".
Did you mean:
pregati
2006 Nov 04
2
[LLVMdev] Port succesful
I made the windows port, the first example compiled and executed correctly.
I am sending a patch so you can test it if i didn't break linux
compatibility.
Otherwise, I will look into deja-gnu testing, perhaps can compile it on
windows. I will
also add other beckend in the future (Sparc, PowerPC). I hope windows using
Visual C++ will be soon officially supported :)
About the problem I had
2006 Feb 21
1
How to install centOS SPRAC
I'd like to know where can i find an installation guide for CentOS SPARC??
I have to install CentOS SPARC on a SunMicrosystem NETRA T1, if someone could help me out with that..
thanks..
---------------------------------
Brings words and photos together (easily) with
PhotoMail - it's free and works with Yahoo! Mail.
-------------- next part --------------
An HTML attachment was
2003 May 22
0
Some warnings when starting Asterisk
Hi,
When I start asterisk with asterisk -vvvvc it works preaty well, but I get
the following warnings:
Warning, flexibel rate not heavily tested!
WARNING[1074494176]: File res_musiconhold.c, Line 462 (moh_register
): Unable to open pseudo channel for timing... Sound may be choppy.
WARNING[1074494176]: File res_musiconhold.c, Line 462 (moh_register
): Unable to open pseudo channel for timing...
2006 Nov 04
0
[LLVMdev] Port succesful
> Otherwise, I will look into deja-gnu testing, perhaps can compile it on
> windows. I will
The deja-gnu testing framework will most likely have to be rewritten to
run on Windows. Its very unix specific.
-Tanya
> also add other beckend in the future (Sparc, PowerPC). I hope windows using
> Visual C++ will be soon officially supported :)
>
> About the problem I had with
2006 Nov 06
0
[LLVMdev] LLVM code emittion and C++ compiler compatibily
Hello, Ziga.
> First the calling conversion. The so called __thiscall conversion on
> VC++ passes arguments on stack, while this pointer is passed
> into ECX register. For GCC, as far as I am aware, the this pointer is
> pushed as if it were a special (first) argument. The fix would
> be preaty simple but we want the bytecode to be OS independant, so we
> cannot change the
2006 Nov 06
2
[LLVMdev] LLVM code emittion and C++ compiler compatibily
Hello!
I have a question how about JIT-ed code and the C++ compiler
compatibily. My project (www.baadengine.org) will use
llvm and we will provide integration of JIT-ed code directly into C++
code. This means that C++ code can call JIT code just
like any other code and JIT-ed code can call C++ code. We will compile
to your bytecode from our BSF format.
The question is if it is possible this