search for: migdalskiy

The original thread on this ICE, including a link to the bug submitted to MS is here: http://lists.cs.uiuc.edu/pipermail/llvmdev/2012-December/056683.html Michael From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Sergiy Migdalskiy Sent: Thursday, April 18, 2013 10:28 To: David Blaikie Cc: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] Patch to compile LLVM with MSVC 2010 >From the DeveloperPolicy.html<http://llvm.org/docs/DeveloperPolicy.html> document I gathered I need to send a patch to this list (which I did); co...

...help me submit it - it's a really simple couple of patches that make LLVM/clang compile on MSVC10 without further modifications. Regards,Sergiy > Date: Wed, 17 Apr 2013 21:56:43 -0700 > Subject: Re: [LLVMdev] Patch to compile LLVM with MSVC 2010 > From: dblaikie at gmail.com > To: migdalskiy at hotmail.com > CC: llvmdev at cs.uiuc.edu > > On Wed, Apr 17, 2013 at 11:36 AM, Sergiy Migdalskiy > <migdalskiy at hotmail.com> wrote: > > In order to get llvm to compile on Windows with MSVC 10, I have to disable > > inline on utostr to avoid internal compiler fail...

In order to get llvm to compile on Windows with MSVC 10, I have to disable inline on utostr to avoid internal compiler failure, and disable _xgetbv call in OsSupportsAVX because it's only defined in MSVC 2012 compiler. The first patch (noinline) is known for many months now. I'm a casual llvm user, and don't know the proper channels to go through to submit a patch. Could someone tell

On Wed, Apr 17, 2013 at 11:36 AM, Sergiy Migdalskiy <migdalskiy at hotmail.com> wrote: > In order to get llvm to compile on Windows with MSVC 10, I have to disable > inline on utostr to avoid internal compiler failure, and disable _xgetbv > call in OsSupportsAVX because it's only defined in MSVC 2012 compiler. The > first patch...