similar to: -ffast-math optimizations impacted by symbol renaming in header files

I think the simplest, most complete, short term fix, would be to call llvm::colorEHFunclets, and to have the relevant instrumentation passes apply the appropriate funclet bundle when inserting function calls. It's not elegant because it means every simple instrumentation pass that inserts regular function calls (ASan, TSan, MSan, instrprof, etc) needs to be funclet-aware. But, it will work,

I think this is the same underlying issue as https://bugs.llvm.org/show_bug.cgi?id=40320. CCing Reid, who's had a bunch of thoughts on this in the past. On 1/11/20, 10:25 AM, "llvm-dev on behalf of Chrulski, Christopher M via llvm-dev" <llvm-dev-bounces at lists.llvm.org on behalf of llvm-dev at lists.llvm.org> wrote: Hi, I've run into a bug with the LLVM

Hello, [sorry for the duplicate post, attempting to fix the formatting of the previous post] Can anybody tell me the intent of the LibCallAliasAnalysis class? I see that to instantiate it, it requires a class derived from the pure virtual class LibCallInfo, but I cannot find any classes in the source tree that derive from LibCallInfo. Is this derived class intended to be supplied from a compiler

Dear R-Community: I am assisting a community college instructor in an introductory statistics class. He has asked me to do this: Read in a file, of filenames, line by line: Student_models.txt : (contains 1500+ filenames) ________________________ Experiment_name_student_name_date_time_Model_number_etc_etc Another_file_name_with_similar_info_as_above And_another And_another_one

I have a new problem: Register RBP is used in a function foo. (I am not allocating RBP to any virtual register, the instances of RBP in function foo are in the machine code when my register allocator starts.) Function foo calls function bar. Register RBP is not saved across the call, though it is live after the call. Function bar includes a virtual register. The code that I'm using to

Hi, I've installed dovecot debian stable(from backports) version (1.0.15). Its great..i just have problem with sieve filters. I use only web tool for creating filters that works for me (avelsieve plugin for squirrelmail). it creates rules, where specified folder has prefix INBOX. Thats fine.. Since dovecot has configured prefix INBOX too. BUT mails are delivered to INBOX.INBOX.test_folder

Hi, I have started one node through libvirt API using its start method. I am trying to stop that node using the *destroy *method provided by the API but I am not able to do so. Instead, I am getting one message saying: *libvir: error: internal error Child process (vmrun -T player stop /root/test_folder/myImage.vmx soft) unexpected exit status 255* Can anybody tell me why I am not able to stop

Hello Teresa, > Without -flto, a.o ends up with a reference to __exp_finite, That’s correct. > which also would not be satifisfied out of libexp.a. That’s not correct. Even if libexp.a would have __exp_finite, it wouldn’t be resolved from libexp.a, because of the behavior described in my first message. > Do you also have an implementation of __exp_finite in your libexp.a? No, I don’t

Hello, Running Samba 3.3.10 on FreeBSD 7.3. Cannot copy a folder with a subfolder and 10 files in the subfolder from an OSX 10.6.4 client to a folder on the Samba server. What happens is that the folder gets copied but not the subfolder and its files. root at aries:/usr/local/etc# testparm Load smb config files from /usr/local/etc/smb.conf Processing section "[homes]" Processing

Dear community, Recently I discovered that llvm gold linker plugin (LLVMgold.so) doesn't add llvm instrinsics symbols to the linker symbol table. I do not claim that something is necessary wrong, just want to share my observations with the community. Brief summary If I create a static library with a custom version of 'exp()' math function and link it as follows: $

A couple questions/notes so I can understand better: Without -flto, a.o ends up with a reference to __exp_finite, which also would not be satifisfied out of libexp.a. Do you also have an implementation of __exp_finite in your libexp.a? Can you build with -fno-builtin, or -fno-builtin-exp etc? That results in a reference to __exp_finite in the .o bitcode (which of course has the same issue I

Hi All, (retrying to post again - somehow message got blocked) I am running 3.2.7-1.fc16.x86_64 (latest FC 16 kernel) I posted regarding this problem earlier, but after some research and found improvement with new kernel version. so I decided to repost in a new thread to clean things up... The intention of this post is to hopefully be useful and point out some performance numbers that devs can

I'm trying to figure out exactly how the intrinsics/libc/libm work in llvm. For example, this code return user defined function: float acos(float x, float y) { return x+y; } float a; void foo(float b, float c) { a = acos(b, c); } But this code returns llvm.intrinsic: float acos(float, float); float a; void foo(float b, float c) { a = acos(b, c); } float acos(float x, float y) {

Hello, I don't know if the result of acos(0.5) == pi/3 is a bug or not. It looks strange to me. Inaki Murillo

Hi Jack, > I am finding that llvm 2.8 rc3 with dragonegg svn built against current > gcc-4_5-branch doesn't appear to allow gfortran to use -ffast-math. Attempting > to compile code using the dragonegg plugin under gcc 4.5.2 with that option produces the error... > > f951: Unknown command line argument '--enable-finite-only-fp-math'. Try: 'f951 -help' >

Jack, > This also seems to be the same failure preventing capacita.f90, gas_dyn.f90, induct.f90, protein.f90, rnflow.f90 and > test_fpu.f90 from compiling. This might be a long-standing fortran frontend bug where bogus trees were created. It was specially workarounded in llvm-gcc. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State

On Wed, Oct 06, 2010 at 08:24:28PM +0400, Anton Korobeynikov wrote: > Jack, > > > This also seems to be the same failure preventing capacita.f90, gas_dyn.f90, induct.f90, protein.f90, rnflow.f90 and > > test_fpu.f90 from compiling. > This might be a long-standing fortran frontend bug where bogus trees > were created. It was specially workarounded in llvm-gcc. > Anton,

Jack, >   Have you considered looking up that bug in FSF gcc bugzilla and pinging it? > The gfortran developers may  have forgotten about it and perhaps it could be > addressed by them for gcc 4.6 (as they are still in stage 1 for a few more weeks). Well, that bug is in bugzilla since gcc 4.2. Since it does not influence "stock" gcc I doubt they will mark it as high priority.

On Wed, Oct 06, 2010 at 09:21:51PM +0400, Anton Korobeynikov wrote: > Jack, > > >   Have you considered looking up that bug in FSF gcc bugzilla and pinging it? > > The gfortran developers may  have forgotten about it and perhaps it could be > > addressed by them for gcc 4.6 (as they are still in stage 1 for a few more weeks). > Well, that bug is in bugzilla since gcc

Hi Duncan, I like the changes to IRBuilder and how the operator can't change it. Looks a lot safer (mistake-wise) and more convenient. This function won't to remove a previously set tag, which could be used by optimisations or inlining. + Instruction *AddFPMathTag(Instruction *I, MDNode *FPMathTag) const { + if (!FPMathTag) + FPMathTag = DefaultFPMathTag; + if (FPMathTag) +