search for: coffeemug

Ok, I just tried the patch with some modifications (added msvc target and used WIN32 instead of __MINGW32__ for preprocessor) and everything worked beautifully. Thanks for the help! On Mon, 7 Mar 2005 20:45:40 -0500, Vyacheslav Akhmechet <coffeemug at gmail.com> wrote: > Reid, > > This patch won't work for me. I compile llvm toolset with MSVC Express > (hence __MINGW32__ won't be defined for me at compile time). I only > try to feed the generated assembly into gcc (pretty much gnu > assembler, I suppose). I don...

...ing > worked beautifully. Thanks for the help! Did you actually try the previous patch? If you compiled llvm-gcc with mingw, it should work, regardless of the compiler you use to compile the LLVM X86 backend with. -Chris > On Mon, 7 Mar 2005 20:45:40 -0500, Vyacheslav Akhmechet > <coffeemug at gmail.com> wrote: >> Reid, >> >> This patch won't work for me. I compile llvm toolset with MSVC Express >> (hence __MINGW32__ won't be defined for me at compile time). I only >> try to feed the generated assembly into gcc (pretty much gnu >> assembl...

Reid, This patch won't work for me. I compile llvm toolset with MSVC Express (hence __MINGW32__ won't be defined for me at compile time). I only try to feed the generated assembly into gcc (pretty much gnu assembler, I suppose). I don't use mingw tools at the earlier stage. However it's obvious for me how to modify the code now (just add MSVC at that line), thanks! I'll try it

Vyacheslav, I've tracked down the change and I have a fix for you to test. The attached patch should be applied to the CVS head (version 1.132) of X86AsmPrinter.cpp in llvm/lib/Target/X86. The patch just includes MINGW targets in the same set of choices that it makes for Cygwin. Could you please try the patch and let me know if it solves your problem? If it does, I'll commit the patch.

> Did you actually try the previous patch? If you compiled llvm-gcc with > mingw, it should work, regardless of the compiler you use to compile > the LLVM X86 backend with. I didn't build llvm-gcc. I just used the front end provided by the online demo on LLVM's webpage.

> a) Make all functions the same type. For example, make them all return > void, take a vector of parameters as the first argument, and a vector > for return values as the second argument. This is something I was considering. I guess I'll end up going with this option. > I don't see how this is a specific challenge with LLVM. It seems to me > that this is a challenge that

> I'm confused. My understanding is that Visual C++ Express does not > include Visual Studio, which is required to build LLVM. Well, Visual C++ Express is a cut down version of Visual Studio. I'm not sure about exact differences between editions but Visual C++ Express does read the .sln files and comes with an excellent C++ compiler. I didn't encounter any problems building llvm

I am having trouble understanding the relationship between LLVM identifiers, stack (alloca) and variables. In particular, when I need to create a variable, what should I use? For instance, consider the following C-like language snippet: int f() { int i = rand(); if(i > 5) i = 1; return i; } Ignoring optimizations, what should I use to represent 'i'? Online demo gives the following

I am currently playing around with llvm using Visual C++ Express (beta). It works flawlessly. It takes a while to get started but once you do, everything is perfect. Make sure to get the latest CVS sources, the 1.4 release doesn't play nice with Visual Studio. Once you do, extract the file I attach to this email into the llvm\win32 folder. Then add llvm/win32\tools folder to a list of

I recently ran into the following problem. I'm prototyping a compiler for a dynamically typed language in which functions are first class objects. Assuming I have something like this: if(rand() > 5) i = define(x, y, z) { return x + y + z; } else i = define(x, y) { return x + y; } At this point I cannot know the type of 'i' at compile time. At runtime 'i' is a

Evan, The problem is that I do not know the type of a target function at compile time. If you consider my code example, I don't know the type of 'i' until runtime (in fact, I can't even know a possible range of types 'i' may assume). Thanks, - Slava. On 4/21/05, Evan Jones <ejones at uwaterloo.ca> wrote: > On Thu, 2005-21-04 at 09:31 -0400, Vyacheslav Akhmechet

Ok, I got home so I have more details. Here's the sample C program: ----------------- C program --------------- #include <stdio.h> int main() { printf("hello world\n"); return 0; } ------------- end C program ------------- This is compiled using llvm online demo into the following llvm code (target removed): ----------------- LLVM code -------------- deplibs

I successfully compiled CVS HEAD yesterday on my win32 machine using Visual C++ Express (2005). I also have Mingw tools installed. I wrote a simple hello world application and generated native assembly code using llvm. When I tried to feed the code into GCC, it rejected it with "junk at the end of line" error messages. Shouldn't GCC be able to assemble this code? I realize win32 port

I'm not sure what causes this. Everything builds fine in Release mode but when I try to do a Debug build I get an error in Transforms (which causes all dependant projects to fail as well). I'm not exactly sure what causes the error, I'll try to investigate tomorrow (unless someone can figure out what it is by then). Below is the output from VS: ------ Build started: Project: