[llvm-commits] [llvm] r133708 - in /llvm/trunk: include/llvm/ include/llvm/Support/ lib/MC/ lib/Target/CppBackend/ lib/Transforms/Scalar/ lib/Transforms/Utils/ lib/VMCore/

Francois Pichet pichet2000 at gmail.com
Mon Jun 27 06:14:38 PDT 2011


On Mon, Jun 27, 2011 at 4:10 AM, Jay Foad <jay.foad at gmail.com> wrote:
> On 27 June 2011 00:57, Francois Pichet <pichet2000 at gmail.com> wrote:
>> On Thu, Jun 23, 2011 at 5:09 AM, Jay Foad <jay.foad at gmail.com> wrote:
>>> Author: foad
>>> Date: Thu Jun 23 04:09:15 2011
>>> New Revision: 133708
>>>
>>> URL: http://llvm.org/viewvc/llvm-project?rev=133708&view=rev
>>> Log:
>>> Reinstate r133513 (reverted in r133700) with an additional fix for a
>>> -Wshorten-64-to-32 warning in Instructions.h.
>>
>> Hi Jay, This commit creates a very weird problem on MSVC where clang
>> test /CodeGen/vla.c stalls in release mode. (but not in debug).
>>
>> I suspect a subtle memory corruption issue that doesn't show up on the
>> various unixes system because we get lucky. Windows .exe are generally
>> easier to crash if there is a memory corruption issue.
>
> Hi Francois,
>
> I've tried running that test under valgrind on Linux, but it doesn't
> show anything.
>
> I'll try building on Windows. What version of MSVC are you using? 32
> or 64 bit? Do you do a Release or Release+Asserts build? Do you use
> cmake?
>

I can reproduce the problem with MSVC2010 SP1 and MSVC 2008.
Targeting win32, Release without assert, with cmake. (cmake is
mandatory if you use MSVC).


on msvc 2010 CodeGen/vla.c is stuck
on msvc 2008 CodeGenObjC/arc.m

If I run the tests from the command line instead of from VisualStudio
I get a different test who is stuck but the failing test is always
within clang/test/CodeGen*/*

You have to run all the tests to get the failure. Individual run will pass.



More information about the llvm-commits mailing list