Displaying 7 results from an estimated 7 matches for "soddi".
Did you mean:
oddi
2012 May 14
0
[LLVMdev] Fwd: Tiny bug in Kaleidoscope sample (FALSE ALARM)
Nope, it seems that the code is correct after all. Perhaps a bit unclear,
but correct. So shame on me!
Cheers,
Mikael
---------- Forwarded message ----------
From: Mikael Lyngvig <mikael at lyngvig.org>
Date: 2012/5/14
Subject: Tiny bug in Kaleidoscope sample
To: llvmdev at cs.uiuc.edu
Hi,
As far as I can tell, there's a tiny error in the sample code for the
Kaleidoscope
2012 May 25
2
[LLVMdev] Minor correction to the Visual Studio documentation
Now I recall what the problem was that I had: My code makes use of the
Win32 API and that means pulling in Windows.h, which again pulls in some
headers that make use of the force_inline thingy, which is not supported
under Windows yet.
I guess if I stuck with portable code, I could probably use Clang for
Windows. Once again, I have to visit the thinking box and figure out what
to do.
But thanks
2012 May 25
0
[LLVMdev] Minor correction to the Visual Studio documentation
Hello Mikael,
> Now I recall what the problem was that I had: My code makes use of the Win32
> API and that means pulling in Windows.h, which again pulls in some headers
> that make use of the force_inline thingy, which is not supported under
> Windows yet.
Or you can use windows.h from mingw :)
--
With best regards, Anton Korobeynikov
Faculty of Mathematics and Mechanics, Saint
2012 May 24
0
[LLVMdev] Minor correction to the Visual Studio documentation/Windows support in general
On Thu, May 24, 2012 at 12:53 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote:
> One project I'd like to complete pretty soon is to go through the build
> instructions, for mingw32, and see if I can't somehow create a mingw64
> build. I believe the 32-bit platform is dying by the hour so I'm rather
> eager to have a mingw64 version of LLVM/Clang. Also, I'd love
2012 May 27
0
[LLVMdev] Linking clang.exe takes more than two hours?
于 2012/5/27 11:04, Mikael Lyngvig 写道:
> Hi,
>
> I'm building using MINGW64 on a very slow system (Intel Atom 330 X2
> 1.6 GHz), but it seems rather odd that the system has been linking
> clang.exe for the past two hours. It appears that a couple of
> gigabytes of virtual memory are being used (causing constant swapping)
> - the system has only 2 GB of physical memory.
2012 May 27
2
[LLVMdev] Linking clang.exe takes more than two hours?
Hi,
I'm building using MINGW64 on a very slow system (Intel Atom 330 X2 1.6
GHz), but it seems rather odd that the system has been linking clang.exe
for the past two hours. It appears that a couple of gigabytes of virtual
memory are being used (causing constant swapping) - the system has only 2
GB of physical memory.
Is this a bug in MINGW64 (binutils 2.22) or is it just too little RAM in
2012 May 24
3
[LLVMdev] Minor correction to the Visual Studio documentation/Windows support in general
>
> the problem is that very few LLVM developers use or know anything about
> Windows.
> The only way for this to change is for people who do know and care about
> Windows
> to step forward, work on improving Windows support, and contribute their
> Windows
> viewpoint to design discussions etc.
>
As it is now, Windows users will quite likely drop LLVM because of the