search for: zakladowi

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 I have problem with deliver dying with signal 11. I'm using postfix + dovecot devliver. If mailbox have many (100+) redirects in sieve or many other sieve rules deliver died. I have tested this in debian etch + dovecot 1.1.18 (compiled from sources) and debian lenny + dovecot 1.1.13 from backports. Sep 7 13:58:19 mail postfix/pipe[5964]: AC6835938: to=<test1 at mx.domain>,

Witam Sieve implementation in dovecot 1.2 have hard-coded limit for max redirect: SIEVE_DEFAULT_MAX_REDIRECTS 4. I have to rise this to much higher value, e.g. 64. Is there possibility to do this another way than recompiling source? Maybe adding an option to dovecot.conf in plugin section will be a good idea. -- Pozdrowienia Maciej Polewczynski Registered Linux user #117725 OGICOM Sp.

> I'm trying to understand how the non-LTO case is supposed to work non-LTO case works because when linker starts it’s job all the llvm intrinsics are already lowered. > Right, which is why I am suggesting that it might be appropriate to build with -fno-builtin (or -fno-builtin-exp) here – > this solves the LTO issue as there will no longer be an llvm intrinsic in the bitcode Yes, I

Hi all, Many of us find ourselves spending a great chunk of time comparing LLVM IR dumps at various stages of compilation pipeline or after a given optimization pass. Said process can be extremely laborious, and this is especially true when comparing shaders or compute modules. Important semantic differences are often difficult to spot because of the irregular naming and ordering of instructions.

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: $

+pcc for thoughts On Fri, Mar 23, 2018 at 9:37 AM, Bakhvalov, Denis <denis.bakhvalov at intel.com > wrote: > 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

Hi, I'm from Intel compiler department. I am proposing the integration of a backend targeting Nios II processor architecture. Nios II is a 32-bit general-purpose RISC processor core designed specifically for the Altera family of FPGAs. All information at about Nios II can be found at Altera website https://www.altera.com/products/processors/support.html, including the current ISA

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