search for: soluz

...you are using is too old in comparison to the one used for the clang compilation. Thanks, -Stella -----Original Message----- From: Gaier, Bjoern <Bjoern.Gaier at horiba.com> Sent: Sunday, October 28, 2018 11:48 PM To: Stella Stamenova <stilis at microsoft.com>; Dennis Luehring <dl.soluz at gmx.net> Cc: llvm-dev <llvm-dev at lists.llvm.org> Subject: RE: [llvm-dev] Building LLVM with VisualStudio 2017 Hey Stella, (Gaier is my last name :0) I do the same steps as you do! The resulting Clang compiler is indeed working. I have problems with the LLVM library. When I build t...

the clang 3.5 loop optimizer seems to jump in unintentional for simple loops the very simple example ---- const int SIZE = 3; int the_func(int* p_array) { int dummy = 0; #if defined(ITER) for(int* p = &p_array[0]; p < &p_array[SIZE]; ++p) dummy += *p; #else for(int i = 0; i < SIZE; ++i) dummy += p_array[i]; #endif return dummy; } int main(int argc, char** argv) {

I’ve missed it. I did a quick search and the only thread I found is back from 2013. Could you please provide me with a link to the thread? François Fayard Founder & Consultant - Inside Loop Tel: +33 (0)6 01 44 06 93 <tel:+33%206%2001%2044%2006%2093> Web: www.insideloop.io <http://www.insideloop.io/> Twitter: @insideloop_io > On 06 May 2015, at 07:21, David Blaikie <dblaikie

>The pdb reading code relies *very heavily* on Windows APIs can you make shure not to have any windows api stuff in the pdb-reader interface so its easy to - if someone wants to - implement an windows-api independent version (support reading under linux etc.) because the pdb format needs to be analysed anyway for writing pdb information on compile/link (in the future) Am 29.01.2015 um 19:20

I've been working on adding pdb reading support to llvm. This started as a tool for dumping info from a pdb (similar to llvm-dwarfdump), which has been checked in and currently has limited support for dumping pdb. There's still more to be done on the pdb dumping tool, but at this point -- to reduce duplicated effort -- I think it makes the most sense to start moving some of this logic

Hi Reid, I'm trying to get a "big picture" view of everything that needs to be done for clang and llvm to support SEH and C++ exception handling for the "msvc" environment. I've put together a list, including work in progress, but I'm guessing that I've missed some details. Can you look this over and tell me if it matches your idea of what needs to be done?

hi llvmdev list im currently investigating a missing optimizer feature in VS2010 - and comparing the VS2010 results with the result of clang 3.1 i've downloaded clang from http://llvm.org/releases/download.html -> Experimental Clang Binaries for Mingw32/x86 clang --version clang version 3.1 (branches/release_31) Target: i686-pc-mingw32 Thread model: posix ----- test.c typedef

addition to my last post: http://groups.google.com/group/llvm-dev/browse_thread/thread/afd85c3f303ec2a9 i know that using static on my globals will remove them - no other compilation unit can then extern the vars but my question is - in this closed szenario clang is "directly" producing the exe - isn't clang aware of that the vars are not in use? btw: the microsoft compiler