Displaying 6 results from an estimated 6 matches for "802160".
2016 Oct 07
2
[cfe-dev] Revisiting our informal policy to support two versions of MSVC
...end next
> week?
>
> As another data point, other than new features or build failures, I just
> had to debug (with the help of Intel folks) a runtime failure because of a
> bug with zero-initialization in MSVC 2013 (see
> https://connect.microsoft.com/VisualStudio/feedback/details/802160 ).
>
> —
> Mehdi
>
>
> On Sep 8, 2016, at 8:38 AM, James Molloy via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
> Thank you both, we appreciate it a lot!
> On Thu, 8 Sep 2016 at 16:37, Aaron Ballman via llvm-dev <
> llvm-dev at lists.llvm.org> wrot...
2016 Oct 17
2
[cfe-dev] Revisiting our informal policy to support two versions of MSVC
...n MSVC 2013 at the end next week?
>
> As another data point, other than new features or build failures, I just had to debug (with the help of Intel folks) a runtime failure because of a bug with zero-initialization in MSVC 2013 (see https://connect.microsoft.com/VisualStudio/feedback/details/802160 <https://connect.microsoft.com/VisualStudio/feedback/details/802160> ).
>
> —
> Mehdi
>
>
>> On Sep 8, 2016, at 8:38 AM, James Molloy via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
>>
>> Thank you both, we...
2016 Oct 19
2
[cfe-dev] Revisiting our informal policy to support two versions of MSVC
...the plug on MSVC 2013 at the end next week?
As another data point, other than new features or build failures, I just had to debug (with the help of Intel folks) a runtime failure because of a bug with zero-initialization in MSVC 2013 (see https://connect.microsoft.com/VisualStudio/feedback/details/802160 ).
—
Mehdi
On Sep 8, 2016, at 8:38 AM, James Molloy via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote:
Thank you both, we appreciate it a lot!
On Thu, 8 Sep 2016 at 16:37, Aaron Ballman via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev a...
2016 Oct 19
2
[cfe-dev] Revisiting our informal policy to support two versions of MSVC
...gt; week?
>
>
>
> As another data point, other than new features or build failures, I just
> had to debug (with the help of Intel folks) a runtime failure because of a
> bug with zero-initialization in MSVC 2013 (see
> https://connect.microsoft.com/VisualStudio/feedback/details/802160 ).
>
>
>
> —
>
> Mehdi
>
>
>
>
>
> On Sep 8, 2016, at 8:38 AM, James Molloy via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
>
>
> Thank you both, we appreciate it a lot!
>
> On Thu, 8 Sep 2016 at 16:37, Aaron Ballman via llvm-dev...
2016 Oct 19
2
[cfe-dev] Revisiting our informal policy to support two versions of MSVC
...gt; week?
>
>
>
> As another data point, other than new features or build failures, I just
> had to debug (with the help of Intel folks) a runtime failure because of a
> bug with zero-initialization in MSVC 2013 (see
> https://connect.microsoft.com/VisualStudio/feedback/details/802160 ).
>
>
>
> —
>
> Mehdi
>
>
>
>
>
> On Sep 8, 2016, at 8:38 AM, James Molloy via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
>
>
> Thank you both, we appreciate it a lot!
>
> On Thu, 8 Sep 2016 at 16:37, Aaron Ballman via llvm-dev...
2016 Sep 08
2
[cfe-dev] Revisiting our informal policy to support two versions of MSVC
Thank you both, we appreciate it a lot!
On Thu, 8 Sep 2016 at 16:37, Aaron Ballman via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> On Thu, Sep 8, 2016 at 11:24 AM, Reid Kleckner via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
> > I can't say I'm excited to support MSVC 2013 for another month, but I'm
> more
> > concerned about the burden on