search for: villans

Thanks for the quick reply! I will keep the DIBuilder and Clang's CGDebugInfo as my reference for now. At the moment I want to stick with generating .ll -- it's somewhat easier for me to debug the output of my compiler that way, and I haven't programmed much in C/C++ for years -- mostly been a JVM guy. But at one point I may want to look into bindings or even creating a bootstrapped

That's a pretty seriously unsafe floating point optimization. It could be done in fast-math mode, but I doubt we currently do it. --Owen On Apr 23, 2013, at 1:12 PM, Erkki Lindpere <villane at gmail.com> wrote: > hi! > > I'm using LLVM 3.2. Does it optimize away llvm.pow(llvm.sqrt(x), 2) to `x` with any settings? I tried with llc -O3, but that didn't do it. >

Thanks for the reply On Fri, Jul 29, 2011 at 2:06 AM, David A. Greene <greened at obbligato.org>wrote: > Erkki Lindpere <villane at gmail.com> writes: > Ok. Do you ever need to grab the address of something on the stack? If > so you're going to need an alloca. AFAIK, it's the only way to generate > an address for a local object. This is by design of the IR and

hi! I'm using LLVM 3.2. Does it optimize away llvm.pow(llvm.sqrt(x), 2) to `x` with any settings? I tried with llc -O3, but that didn't do it. Would be nice to write |v|² in my language ('v' being a 2D vector say and |...| and ...² being two separate infix "operators") -- when I could compare squares of lengths as well as lengths, and know that the sqrt is optimized

On Wed, Mar 20, 2013 at 2:21 PM, Erkki Lindpere <villane at gmail.com> wrote: > Hi, > > I wanted to add debug info to my language (compiler written in Scala, > outputs .ll files), but I found it really hard to do based on the > documentation provided at http://llvm.org/docs/SourceLevelDebugging.html(I looked at the specific doc for LLVM 3.0 though) > > With LLVM 3.0, DI

Erkki Lindpere <villane at gmail.com> writes: > I want to experiment with avoiding mutable state as far as I can. At > the moment there are no mutable variables -- only immutable value > types (numerics, bool, vectors, tuples) and I've been doing everything > in LLVM registers. The compiler doesn't generate a single alloca, load > or store at the moment. Ok. Do you

Hi, I wanted to add debug info to my language (compiler written in Scala, outputs .ll files), but I found it really hard to do based on the documentation provided at http://llvm.org/docs/SourceLevelDebugging.html (I looked at the specific doc for LLVM 3.0 though) With LLVM 3.0, DI version 8 (which is documented there) seemed to work, except DW_TAG_auto_variable for which I used version tag 11

Hi, I'm a newbie when it comes to compilers (and even close-to-machine coding), but recently started working on my own language and am using LLVM as the mid/backend. Currently I'm generating .ll files from a front-end written in Scala. The language is not really serious, just a way to learn more about compilers (and LLVM) and maybe serve as a base for further experiments. It's

Hello, Am Dienstag, 23. April 2013, 13:26:19 schrieb Owen Anderson: > That's a pretty seriously unsafe floating point optimization. It could be > done in fast-math mode, but I doubt we currently do it. I just saw this thread and wonder why it's "seriously" unsafe? I see only one problematic corner case. For x >= 0.0 the result cannot lose precision. For x = NaN the

In 1.1.5 the sound/music in games played allright. Since 1.1.6 it skips badly - plays for a couple of seconds, then stops for half a second, then plays again, then skips and so on. Happens on every game on Steam - Team Fortress 2, Everyday Shooter, Peggle Extreme - and also without Steam - Icy Tower. I have Razer Barracuda AC-1 sound card. I've found that in Winecfg when I choose Alsa driver