search for: msvc9

...her platforms. > > Another reason is that by limiting the build to X86, there is a > smaller probability of a build failure with a toolset which is not > checked on a day-by-day basis, as msvc is. MSVC *is* continuously checked; see http://google1.osuosl.org:8011/builders/clang-i686-xp-msvc9. Anyone who breaks the MSVC build will get a nastygram from buildbot. -Eli

Hi *, at the moment the build of clang is broken on MSVC 9.0 (according to buildbot http://google1.osuosl.org:8011/console at least since 2010-02-06 01:02:15) due to some strange template name lookup problems.,,, 97>FlatStore.cpp 97>D:\public\zorg\buildbot\osuosl\slave\clang-i686-xp-msvc9\llvm\include\llvm/ADT/ImmutableIntervalMap.h(98) : error C3861: 'MarkImmutable': identifier not found 97> D:\public\zorg\buildbot\osuosl\slave\clang-i686-xp-msvc9\llvm\include\llvm/ADT/ImmutableIntervalMap.h(96) : while compiling class template member function 'llvm::ImutAVLTr...

Am 09.08.09 23:36, schrieb Eli Friedman: > > MSVC *is* continuously checked; see > http://google1.osuosl.org:8011/builders/clang-i686-xp-msvc9. Anyone > who breaks the MSVC build will get a nastygram from buildbot. > Please note that the MSVC buildbot only builds the X86 target at the moment. I don't know why though.

...ne else should sign >> off on it. > > This seems ok to me, please commit. One minor comment: Committed. It would be useful if someone could test if this works on Windows, the msvc buildbot was all red before my commit, failing here: G:\public\zorg\buildbot\osuosl\slave\clang-i686-xp-msvc9\llvm\include\llvm/Support/IRBuilder.h(133) : error C3861: 'InsertHelper': identifier not found > > +++ b/lib/Support/Regex.cpp > > + // Allocate pmatch with at least one element. > + pmatch = new llvm_regmatch_t[nmatch > 0 ? nmatch : 1]; > + pmatch[0].rm_so = 0; &...

Eli Friedman <eli.friedman at gmail.com> writes: > MSVC *is* continuously checked; see > http://google1.osuosl.org:8011/builders/clang-i686-xp-msvc9. Anyone > who breaks the MSVC build will get a nastygram from buildbot. This is new news for me. If the developer who broke the msvc build receives a nastygram, would he urged to fix it when he has no msvc compiler and probably no Windows machine either? The "don't break the build&qu...

On Sun, Aug 9, 2009 at 3:35 PM, Óscar Fuentes<ofv at wanadoo.es> wrote: > Eli Friedman <eli.friedman at gmail.com> writes: > >> MSVC *is* continuously checked; see >> http://google1.osuosl.org:8011/builders/clang-i686-xp-msvc9.  Anyone >> who breaks the MSVC build will get a nastygram from buildbot. > > This is new news for me. > > If the developer who broke the msvc build receives a nastygram, would he > urged to fix it when he has no msvc compiler and probably no Windows > machine either? The &q...

Eli Friedman <eli.friedman at gmail.com> writes: > On Sun, Aug 9, 2009 at 10:03 AM, Óscar Fuentes<ofv at wanadoo.es> wrote: >> I think most LLVM users on Windows are interested on X86 only. This >> saves a lot of time on the build process and creates smaller >> executables. Anyways, it they want all targets, it is simply a matter of >> passing

On Aug 28, 2009, at 1:53 AM, Daniel Dunbar wrote: > Nice! > > This looks good to me but probably Chris or someone else should sign > off on it. This seems ok to me, please commit. One minor comment: +++ b/lib/Support/Regex.cpp + // Allocate pmatch with at least one element. + pmatch = new llvm_regmatch_t[nmatch > 0 ? nmatch : 1]; + pmatch[0].rm_so = 0; + pmatch[0].rm_eo =

On Sun, Aug 9, 2009 at 10:03 AM, Óscar Fuentes<ofv at wanadoo.es> wrote: >> Also, now msvc support multiple target. So it's better to set it as >> ${LLVM_ALL_TARGETS} >> It's can working, why not set it to:. > > I think most LLVM users on Windows are interested on X86 only. This > saves a lot of time on the build process and creates smaller >

I have filed a number of problem reports about getting the LLVM test infrastructure working for an environment with: Windows + MSVC9 + Cmake + NMake makefiles + MKS. (MKS provides unix-like tools for Windows, but based on very old versions, so they have quirky or minimal compatibility with GNU tools.) http://llvm.org/bugs/show_bug.cgi?id=9689 - Fix Cmake generation of compile_cxx for MSVC - Oscar already applied a fix. Thanks!...

Nice! This looks good to me but probably Chris or someone else should sign off on it. There were two minor warnings on Darwin: -- In file included from /Volumes/Data/Users/ddunbar/llvm/lib/Support/regexec.c:81: /Volumes/Data/Users/ddunbar/llvm/lib/Support/regengine.inc: In function 'sbackref': /Volumes/Data/Users/ddunbar/llvm/lib/Support/regengine.inc:665: warning: control reaches end of