search for: thonermann

On 02/19/2015 04:28 PM, Renato Golin wrote: > On 19 February 2015 at 19:58, Tom Honermann <thonermann at coverity.com> wrote: >> The effort isn't always so small for us however. It has generally taken us >> about a month to upgrade and vet a new Clang release. The Clang release >> cadence is faster than ours, so timing isn't always great (not a complaint, >> jus...

On 02/18/2015 04:57 PM, Renato Golin wrote: > On 18 February 2015 at 21:45, Tom Honermann <thonermann at coverity.com> wrote: >> Unfortunately, we don't currently have the resources to do so. When we >> upgrade, we upgrade to the most recent release and perform testing on top of >> it. > > One safe way of doing so, and would help us without adding much > efforts t...

On 02/18/2015 04:12 PM, Renato Golin wrote: > On 18 February 2015 at 20:59, Tom Honermann <thonermann at coverity.com> wrote: >> My company also does not use ToT. Being able to associate a product with a >> well-known release is *very* important to us. It enables communication with >> our customers. It allows us to determine compatibility between our Clang >> derived p...

On 02/18/2015 03:01 PM, Renato Golin wrote: > So it seems that you're one of the very few people that doesn't use > ToT. Almost everyone else uses it and the progress of LLVM kind of > assume you do. My company also does not use ToT. Being able to associate a product with a well-known release is *very* important to us. It enables communication with our customers. It allows

I checked out llvm/trunk today and found that it failed to build successfully on Linux when 'configure' was invoked with '--disable-shared' and CFLAGS included '-static'. The attached patch modifies a few Makefiles to prevent attempts to build shared libraries when ENABLE_SHARED is not set to 1. Apply the patch in the LLVM root directory with 'patch -p1 ...'

On 12/9/2011 8:23 AM, Seb wrote: > This thread is not to discuss how relevant this example is. I just would > like to know: > a) If people think that adding an option to disable a specific pass is > useful. Yes, a peer of mine recently wanted such an option to disable individual passes in order to 1) narrow in on a bug in one of them that affected stack back tracing, and 2) provide

On 2/22/2012 7:29 AM, Sevak Sargsyan wrote: > Hi all, > I have problem with debugging clang, gdb does not stop in function > ParseFrontendArgs, the function works because I wrote errs() and I saw > it in command line, > I also wrote __asm__("int $3") in ParseFrontendArgs but it does not help. Are you debugging the correct process? Note that invocations of