similar to: [LLVMdev] _FORTIFY_SOURCE warnings

"Hassan, Ahmad" <ahmad.hassan at sap.com> writes: > I would like to ask if LLVM provides a utility function like > 'isMallocCall' to check if the 'call' instruction is calling some > 'foo' user defined function? > > If there is no such utility function then I am thinking to do this in > the following way: > > bool testFoo(CallInst

Hi Ahmad, If the Makefile contains only this command, then it is not worth spending time on GoldPlugin. If you are building a large project, then it will be simpler to use GoldPlugin. The steps you are using seem right. You can possibly combine the last two steps (3&4) using only 1 clang command. clang -g -O2 -o .libs/mergedexe .libs/mergedbc.bc -pthread -Wl,--export-dynamic

Hi Ahmad, Yes, merging works good. However, my problem is like this - I have a C library which consists of 1000's of functions spread through various files. The functions do not have dependency amoung each other. I want to link only relavant files( files which have functions called from my application). Since ar has a global symbol table, I believe it should be faster to look for a symol in

Hi All, I have modified the Makefile inside llvm/tools/clang and added the following flag: CPP.Flags += -D_FORTIFY_SOURCE=0 But when I build clang using 'make' then I get lot of warnings like: <command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined [enabled by default] <built-in>:0:0: note: this is the location of the previous definition Is this expected

--- configure.ac | 23 ++------------------ m4/ax_add_fortify_source.m4 | 53 +++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 55 insertions(+), 21 deletions(-) create mode 100644 m4/ax_add_fortify_source.m4 diff --git a/configure.ac b/configure.ac index 8576cae5..c5b63370 100644 --- a/configure.ac +++ b/configure.ac @@ -393,9 +393,7 @@ fi dnl If debugging is

I tested also with a clean git source. Something wrong with ole32. Code: -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body -Wstrict-prototypes -Wtype-limits -Wwrite-strings -fno-omit-frame-pointer -Wpointer-arith -Wlogical-op -I/usr/include/freetype2 -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=0 -o tmarshal_i.o tmarshal_i.c

Hi, I would like to ask if LLVM provides a utility function like 'isMallocCall' to check if the 'call' instruction is calling some 'foo' user defined function? If there is no such utility function then I am thinking to do this in the following way: bool testFoo(CallInst *CI) { Function *Callee = CI->getCalledFunction(); if (Callee->getName() == "foo")

On 29 March 2018 at 09:43, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > > On 28.03.2018 22:14, Odhiambo Washington wrote: > > > > On 27 March 2018 at 20:06, <aki.tuomi at dovecot.fi> wrote: > >> Hi! >> >> We are releasing v2.3.1, which mostly consists of bug fixes for 2.3.0, >> and few improvements. This is also available via

Hi Ahmad, On 03/01/13 16:26, Hassan, Ahmad wrote: > Hi Team, > > I am migrating one of the Pass that was written for llvm2.2 or older to llvm3.1. > The code snippet looks like the following: > > Constant *func; > > void add( Module *M) { > > func = M->getOrInsertFunction("func", Type::getVoidTy(M->getContext()), NULL); this function has no

On 29 March 2018 at 13:04, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > > On 29.03.2018 10:36, Odhiambo Washington wrote: > > > > On 29 March 2018 at 09:43, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > >> >> >> On 28.03.2018 22:14, Odhiambo Washington wrote: >> >> >> >> On 27 March 2018 at 20:06, <aki.tuomi at

On 29 March 2018 at 13:26, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > > On 29.03.2018 13:14, Odhiambo Washington wrote: > > > > On 29 March 2018 at 13:04, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > >> >> >> On 29.03.2018 10:36, Odhiambo Washington wrote: >> >> >> >> On 29 March 2018 at 09:43, Aki Tuomi

Hi, Tried to build dovecot-2.3.4 on Solaris 11 x86 and it fails at configure part. I just went checked and it last version it works on is v2.3.2.1 Version 2.3.2.1 (OK) # ./configure .... checking Linux compatible mremap()... no checking whether shared mmaps get updated by write()s... yes checking whether fd passing works... yes ... Version 2.3.4 (FAIL) .... checking Linux compatible

Hi Ahmad, On 17/01/13 14:56, Hassan, Ahmad wrote: > Hi All, > > I am migrating a build system of an existing project from ‘Object files’ based > executable generation to ‘LLVM Bitcode’ files based exe generation and applying > OPT pass to LLVM Bitcode. I found out the following 4 step procedure. Please let > me know if this is the right procedure or is there any other easy way

On 27 March 2018 at 20:06, <aki.tuomi at dovecot.fi> wrote: > Hi! > > We are releasing v2.3.1, which mostly consists of bug fixes for 2.3.0, and > few improvements. This is also available via https://repo.dovecot.org if > you want packages. libsodium support didn't get into this build, due to > build environment issues, but 2.3.2 will contain it. > > * Submission

Hi Duncan, > 4.gcc -g -O2 -o .libs/mergedexe .libs/mergedbc.s -pthread > -Wl,--export-dynamic .libs/lib1.a -lssl -lcrypto -ldl -pthread .libs/lib2.so >if you pass -O4 rather than -O2 to clang I think it will in essence do this all >for you already. It might even do the link time optimization for you at -O2 >even, I'm not sure. No, if I use clang for producing

On Tue, 5 Feb 2019 at 20:32, Aki Tuomi via dovecot <dovecot at dovecot.org> wrote: > Due to DMARC issues some people have failed to receive the latest security > information, so here it is repeated for both releases: > > 2.3.4.1 > > https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz > https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz.sig >

On Tue, 5 Feb 2019 at 20:32, Aki Tuomi via dovecot <dovecot at dovecot.org> wrote: > Due to DMARC issues some people have failed to receive the latest security > information, so here it is repeated for both releases: > > 2.3.4.1 > > https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz > https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz.sig >

On 29.03.2018 10:36, Odhiambo Washington wrote: > > > On 29 March 2018 at 09:43, Aki Tuomi <aki.tuomi at dovecot.fi > <mailto:aki.tuomi at dovecot.fi>> wrote: > > > > On 28.03.2018 22:14, Odhiambo Washington wrote: >> >> >> On 27 March 2018 at 20:06, <aki.tuomi at dovecot.fi >> <mailto:aki.tuomi at dovecot.fi>>

On 29.03.2018 13:14, Odhiambo Washington wrote: > > > On 29 March 2018 at 13:04, Aki Tuomi <aki.tuomi at dovecot.fi > <mailto:aki.tuomi at dovecot.fi>> wrote: > > > > On 29.03.2018 10:36, Odhiambo Washington wrote: >> >> >> On 29 March 2018 at 09:43, Aki Tuomi <aki.tuomi at dovecot.fi >> <mailto:aki.tuomi at

Oh, so manual compile should NOT work and it's okay or am I missing something? On Tue, 5 Feb 2019 at 23:26, The Doctor <doctor at doctor.nl2k.ab.ca> wrote: > On Tue, Feb 05, 2019 at 11:18:45PM +0300, Odhiambo Washington via dovecot > wrote: > > On Tue, 5 Feb 2019 at 20:32, Aki Tuomi via dovecot <dovecot at dovecot.org> > > wrote: > > > > > Due to