similar to: [LLVMdev] X + 0.0

On Jul 24, 2010, at 2:59 AMPDT, Jochen Wilhelmy wrote: > Hi! > > in visitFAdd I found this comment: > > // Check for X+0.0. Simplify it to X if we know X is not -0.0. > > Why is it not allowed to simplify X + 0.0 = X when X may be > -0.0? Because -0.0 + 0.0 is 0.0 and not -0.0? > > For me it would be great if strict floating point processing could > be switched

> > The DAGCombiner appears to do both of these with -enable-unsafe-fp-math . > But isn't the DAGCombiner a part of the back-end? Is it possible to get llvm ir out of the DAGCombiner? Do you mean the SelectionDAG? I further process llvm ir and therefore need a "best possible" optimization on llvm ir. -Jochen

> > Currently we don't do any unsafe-math opts in InstCombine. Not sure > if this is policy or if it's just that nobody's implemented it. > perhaps in can be implemented using the existing flag -enable-unsafe-fp-math. what do you think? -Jochen

On 25.11.2010 23:56, Michael Spencer wrote: > On Nov 25, 2010, at 5:01 PM, Jochen Wilhelmy <j.wilhelmy at arcor.de > <mailto:j.wilhelmy at arcor.de>> wrote: > >> Hi! >> >> Of course nobody wants to implement unicode support for windows >> because windows should support an utf8-locale and windows is obsolete >> anyway ;-) >> >> But

Hi! These warnings and errors might be interesting to you when compiling rev. 116572 of llvm and clang on windows: \llvm\utils\killthedoctor\system_error.h(260) : error C2065: 'EAFNOSUPPORT' : undeclared identifier and many similar errors regarding the system error constants. msdn says it's WSAEAFNOSUPPORT instead of EAFNOSUPPORT (prepend WSA... to all system error constants)

Hi! I have a module containing a constant e.g. @input = global %0 zeroinitializer, align 16 when I copy the global into another module I use newGlobal->copyAttributesFrom(global); but the new module now has @input = external global %0, align 16 i.e. the zeroinitializer is missing. how do I set it or copy it from the other global? -Jochen

Hi! > sin/cos etc should already be handled by lib/Analysis/ConstantFolding.cpp. > Thanks for the hint and it works! Now I have a new Problem: I have this function: float foo(float a, float b) { float x = a * b * 0.0f; return cos(0.5) * sin(0.5) * x; }; after compiling it with clang (cpp mode) and renaming _ZSt3sinf to sin and _ZSt3cosf to cos I get the following: define

On Nov 25, 2010, at 5:01 PM, Jochen Wilhelmy <j.wilhelmy at arcor.de> wrote: > Hi! > > Of course nobody wants to implement unicode support for windows > because windows should support an utf8-locale and windows is obsolete > anyway ;-) > > But there is a simple solution: use boost::filesystem::path everywhere you > use file names and paths, for example in

Hi! Of course nobody wants to implement unicode support for windows because windows should support an utf8-locale and windows is obsolete anyway ;-) But there is a simple solution: use boost::filesystem::path everywhere you use file names and paths, for example in clang::FileManager::getFile. With version 3 opening a file is easy: std::fstream file(path.c_str()). Internally

On Jul 26, 2010, at 2:52 PMPDT, Jochen Wilhelmy wrote: >> Currently we don't do any unsafe-math opts in InstCombine. Not >> sure if this is policy or if it's just that nobody's implemented it. >> > perhaps in can be implemented using the existing flag -enable-unsafe- > fp-math. > what do you think? I don't see any good reason these opts shouldn't

On 3 March 2010 11:56, Jochen Wilhelmy <j.wilhelmy at arcor.de> wrote: > > the sin and cos calls are folded, but not the mul by zero. > Is x*0 => 0 true if isnan(x)? And cos(x)*sin(x) makes me desperately want to fold it to sin(2*x)/2, but I suppose that's not allowed either.

On Jul 26, 2010, at 12:38 PMPDT, Jochen Wilhelmy wrote: > >> >> The DAGCombiner appears to do both of these with -enable-unsafe-fp- >> math . >> > But isn't the DAGCombiner a part of the back-end? Is it possible to > get llvm ir > out of the DAGCombiner? Do you mean the SelectionDAG? I mean the pass found in DAGCombiner.cpp, which works on the

Now I have -DLLVM_INCLUDE_EXAMPLES:BOOL=OFF but Kaleidoscope is still there and selected for build (-G "Visual Studio 9 2008") -Jochen

Hi! Is it possible that you add an example how to write a .o with llvm? Just like examples/ModuleMaker but instead of printing to stdout writing a .o file as starting point for the new MC functionality. -Jochen

Hi! when compiling projects using llvm 2.9 and ms vc 10 I get these warnings: 1>e:\Jochen\Lib\lib\include\llvm/Use.h(218): warning C4624: 'llvm::AugmentedUse' : destructor could not be generated because a base class destructor is inaccessible 1>C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\stdint.h(72): warning C4005: 'INT8_MIN' : macro redefinition

On Fri, 26 Nov 2010 09:28:17 -0500 Michael Spencer <bigcheesegs at gmail.com> wrote: > On Fri, Nov 26, 2010 at 4:00 AM, Jochen Wilhelmy > <j.wilhelmy at arcor.de> wrote: > > No, this post was prompted since I switched to boost::filesystem > > version 3 in my own code and llvm/clang 2.8 > > was the only lib with no unicode support on windows. > > Will your

On Fri, Nov 26, 2010 at 4:00 AM, Jochen Wilhelmy <j.wilhelmy at arcor.de> wrote: > No, this post was prompted since I switched to boost::filesystem version 3 > in my own code and llvm/clang 2.8 > was the only lib with no unicode support on windows. > Will your code be api compatible to boost::filesystem? No. boost::filesystem makes extensive use of exceptions, which LLVM is

Hello Jochen- Your expectation is incorrect, I'm afraid. Typically this would be expanded to something like this: … %cmp = … br i1 %cmp, label %ternary.true, label %ternary.false ternary.true: %truevalue = … br label %ternary.end ternary.false: %falsevalue = … br label %ternary.end ternary.end: %value = phi %type [%truevalue, %ternary.true], [%falsevalue,

Hi! In DataTypes.h (generated from DataTypes.cmake) there is an extra code path for Visual C. This can produce macro redefinitions for INT8_MAX, INT8_MIN etc. since other headers may also define them. Therefore please protect the macros like INT8_C etc. Also it would be nice if the auto-generated HAVE_STDINT_H and HAVE_INTTYPES_H would be used also for Visual C since it is possible to add them

Am 29.12.2011 19:52, schrieb Reid Kleckner: > I think Chris is saying that the and is necessary because with your i1 > trunc you're ignoring all of the high bits. The and implements that. > If you don't want this behavior, don't generate the trunc in the > first place and just compare the full width to zero. But if a backend sees trunc from i8 to i1 it should know