similar to: [LLVMdev] xcode 4 and clang+llvm

That's because instructions have a location associated with them, not a compile unit. -eric On Thu, Oct 4, 2012 at 12:46 PM, George Baah <georgebaah at gmail.com> wrote: > I used DILocation instead of DICompileUnit and it works. Hmmm, interesting. > > George > > On Thu, Oct 4, 2012 at 1:33 AM, George Baah <georgebaah at gmail.com> wrote: >> >> Here is

I used DILocation instead of DICompileUnit and it works. Hmmm, interesting. George On Thu, Oct 4, 2012 at 1:33 AM, George Baah <georgebaah at gmail.com> wrote: > Here is the code. I am running on llvm 3.1 on Lion (Mac 10.7.4) > > *string getFileDirectory*(*const* Instruction &I){ > > MDNode *MD = I.getMetadata("dbg"); > > DICompileUnit

Here is the code. I am running on llvm 3.1 on Lion (Mac 10.7.4) *string getFileDirectory*(*const* Instruction &I){ MDNode *MD = I.getMetadata("dbg"); DICompileUnit compileUnit(MD); return compileUnit.getDirectory().str(); } George On Wed, Oct 3, 2012 at 12:40 PM, Eric Christopher <echristo at gmail.com>wrote: > Without knowing the code that you've written

Hmmm, but it has a getDirectory function. -G On Thu, Oct 4, 2012 at 3:50 PM, Eric Christopher <echristo at gmail.com> wrote: > That's because instructions have a location associated with them, not > a compile unit. > > -eric > > On Thu, Oct 4, 2012 at 12:46 PM, George Baah <georgebaah at gmail.com> wrote: > > I used DILocation instead of DICompileUnit and

You should probably think of the DIFooBar constructors like reinterpret-casts, not "go find the thing I actually want" functions. If you hand DICompileUnit() a node that is not a compile-unit metadata node, it's not going to tell you that you goofed. If you _did_ have a CU metadata node, then DICompileUnit's getDirectory() would work just fine. But you don't. --paulr

Downloaded Xcode 4.3 for Lion from the app store, and am following the tutorial for installing wine: http://www.davidbaumgold.com/tutorials/wine-mac/ When I get to part 3 and it tells me to type the following code into terminal Code: $ sudo port install wine I get the following message: Code: xxx-xxx-macbook-pro:~ Kaoss$ sudo port install wine Password: Warning: xcodebuild exists but

Apologies if this isn't the right list for this post, looking for some guidance on compiling rsync on OS X 10.8 Mountain Lion having recently upgraded, including XCode 4.4. > ./prepare-source ~/Code/rsync OSXPatched at 984bc92 make: Nothing to be done for `conf'. > ./configure

Without knowing the code that you've written and the IR that you're running on I'm not sure what I can do to help you. -eric On Wed, Oct 3, 2012 at 9:32 AM, George Baah <georgebaah at gmail.com> wrote: > Yeah, It looks like I am doing exactly what's in Dwarf*.cpp files, yet I am > getting blanks. > > George > > On Tue, Oct 2, 2012 at 2:10 PM, Eric

Yeah, It looks like I am doing exactly what's in Dwarf*.cpp files, yet I am getting blanks. George On Tue, Oct 2, 2012 at 2:10 PM, Eric Christopher <echristo at gmail.com> wrote: > On Tue, Oct 2, 2012 at 11:00 AM, George Baah <georgebaah at gmail.com> wrote: > > Hi Guys, > > How does one get the directory of the compilation unit in llvm? > > I am using

There is also the LowerSwitch pass that converts switch instructions to a sequence of branches. On May 6, 2013, at 1:24 PM, George Baah <georgebaah at gmail.com> wrote: > I mean an llvm Pass that transforms switch statements into if statements. For example, if I have code with switch statements then running the pass will convert all switches to ifs in the bytecode. > > George

I mean an llvm Pass that transforms switch statements into if statements. For example, if I have code with switch statements then running the pass will convert all switches to ifs in the bytecode. George On Mon, May 6, 2013 at 4:20 PM, Hal Finkel <hfinkel at anl.gov> wrote: > ----- Original Message ----- > > From: "George Baah" <georgebaah at gmail.com> > >

Hi Everyone, When I compile a program with clang with debug symbols enabled and I try to run it using the JIT (lli) I get the following error message. I am running on Lion (10.7.4). Thanks. George >> pseudo instructions should be removed before code emission UNREACHABLE executed at /Users/JD/Software/llvm3.1/llvm-3.1.src/lib/Target/X86/X86CodeEmitter.cpp:736! 0 lli

I just noticed that the clang in Xcode 3.2.2 was bumped to 1.0.2. How does the Apple clang versioning numbering relate to that used for the llvm.org version of clang? In particular, what version of clang will llvm 2.7 ship with? I assume that Xcode 3.2.2 must be using clang 2.6, no? Jack

On Feb 28, 2011, at 8:07 PM, Félix Cloutier wrote: > I'm using Xcode 3 to program with LLVM and Clang (both about yesterday's latest revisions), and when I compile, I get 1501 link-time warnings. All those I read were about symbol visibility. Here's an example: > > ld: warning: namespace::class::method() has different visibility (default) in

On Mon, Sep 5, 2011 at 6:16 PM, S. Bharadwaj Yadavalli <bharadwajy at gmail.com> wrote: > Hi, > > Is there some place I can get instructions to load, build and debug > LLVM and/or Clang using XCode on Mac OSX? > > Sorry if this is an FAQ - my (possibly quick) search did not yield an answer. You can generate an XCode project using CMake. See

I don’t think Apple disable assertion on the release build. I remember having clang and llvm crash because of assertion failure regularly at some point in the past. Nowadays, it is far more unusual to get a clang crash, so I can’t tell, but I doubt they change the configuration. > Le 20 nov. 2018 à 16:32, Jack Howarth via cfe-dev <cfe-dev at lists.llvm.org> a écrit : > > The

I think It has to do with the option --disable-optimized. Without that option llvm builds in release mode and everything works fine. Is there something being omitted in the makefiles when building in debug mode? I am running on Mac OSX Lion. George On Tue, Aug 21, 2012 at 8:02 AM, Tobias Grosser <tobias at grosser.es> wrote: > On 08/21/2012 01:44 PM, George Baah wrote: > >>

Hello LLVM/Clang developers, We recently switched to use the same clang version on all our platforms. This included switching from apple-clang from xcode to a pre-built binary we downloaded from llvm.org. We noticed that this actually came with a pretty big performance regression in compile times. If we do the simplest test program like this: #include <string> #include <iostream>

Hi, Is there some place I can get instructions to load, build and debug LLVM and/or Clang using XCode on Mac OSX? Sorry if this is an FAQ - my (possibly quick) search did not yield an answer. Thanks, Bharadwaj

Apple's clang in Xcode 5.1 (as for building with the iOS 7.1 SDK) throws an error about the (gcc-specific?) -fforce-addr option being unknown, which clang now thinks is evil and should abort compilation. It looks like this also hits OS X 10.9 builds, as I see there's a patch for theora in MacPorts for this issue: https://trac.macports.org/ticket/42934 Attached is a quick-fix patch to