[LLVMdev] LLVM command options in Visual Studio

Seung Jae Lee lee225 at uiuc.edu
Fri Apr 6 06:52:09 PDT 2007

Thank you for your kind explanation.
I did it as you mentioned.
That is, I set '-march=x86 hello.bc' in the Command Arguments.
(I also set my compiled LLC, i.e., LLVM_ROOT_DIR\win32\debug\llc.exe, in the property name Command.)

But, when I made a breakpoint in main( ) of llc.cpp and then started to debug I found the 'InputFilename'(llc.cpp:176) is shown like {???}. Therefore it didn't proceed further, spitting out 'bytecode didn't read correctly.'
(Of course, my bytecode was trasferred to my computer as binary.)

Would you mind telling me what seems my problem?
Thank you so much.

Seung Jae Lee

---- Original message ----
>Date: Thu, 05 Apr 2007 23:01:42 -0700
>From: Jeff Cohen <jeffc at jolt-lang.org>  
>Subject: Re: [LLVMdev] LLVM command options in Visual Studio  
>To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu>
>Seung Jae Lee wrote:
>> Hello.
>> I wonder how I can use the options of LLVM commands in Visual Studio Debugging mode.
>> For example, 
>> If I want to follow the pass on 'llc -march=x86 hello.bc' in the Visual Studio's debuggin mode, how can I let it know the options such as '-march=x86 hello.bc'?
>> I can set the breakpoint in main() in llc.cpp but I can't let it cognize that I want X86 assembly code from hello.bc.
>> Forgive my ignorance.
>> Thanks, 
>> Seung Jae Lee
>In the Solution Explorer, right click on llc and select Properties.  
>This brings up the "llc Property Pages" dialog box.  Select Debugging in 
>the left pane.  In the right pane, you'll see a property named Command 
>Arguments.  Set it to whatever you want.
>The Solution Explorer is is either at the far left or far right of the 
>window.  If you don't see it, you can bring it up by selecting it from 
>the View menu.  You'll also need to set llc as the startup project; 
>again, right click on llc and click "Set as StartUp Project".
>LLVM Developers mailing list
>LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu

More information about the llvm-dev mailing list