C ++ AMP:什么时候lambda可能会错误地正确执行? [英] C++ AMP: When may a lambda falsely appear to execute correctly?

问题描述

嗨！

我想问C ++ AMP开发人员一个普遍的问题，该问题由线程"C ++ AMP const数组accelerator_view成员和lambda结果无一例外地破损"中的问题提示.

您能否提供所有已知情况的详尽清单(由于错误，设计，驱动程序问题或未由编译器警告捕获的程序员错误)，在这些情况下C ++ AMP lambda可能会错误地正确执行(即没有任何形式) 异常或以其他方式明显指示程序员(或用户)出了什么问题?

我对在Windows 7、8和8.1(以及相应的服务器版本)上针对x64的VS 2012和VS 2013感兴趣.另外，如果您已经知道由于VS 2014中的设计而引起的任何此类问题，我也会对此感兴趣.

我是否正确假设您的意图是将阻止lambda以书面形式执行的所有问题都报告为程序员的异常?

干杯，
T

Hi!

I wanted to ask the C++ AMP developers a general question prompted by the issue in thread "C++ AMP const array accelerator_view member and broken lambda result without exception".

Can you please provide an exhaustive list of all situations known to you (due to bugs, design, driver issues, or programmer error not caught by compiler warning) where a C++ AMP lambda may falsely appear to execute correctly, i.e., without any kind of exception or otherwise obvious indication to the programmer (or user) that something went wrong?

I am interested in both VS 2012 and VS 2013 targeting x64 on Windows 7, 8 and 8.1 (and corresponding server versions). Also, if you already know of any such issues due to design in VS 2014 I would be interested in that too.

Am I correct in assuming that your intention is that all issues preventing a lambda from executing as written should be reported as exceptions to the programmer?

Cheers,
T

推荐答案

TwoPointSevenOh，

Hi TwoPointSevenOh,

关于您的最后一个问题-是的，目的是应该通过运行时异常或在最坏的情况下导致崩溃来诊断系统中的每个错误.静默地给出不好的结果是最严重的错误类别之一， 并且我们打算以最高优先级解决此类问题.

Regarding your last question -- yes, the intention is that every fault in the system should be diagnosed either by a runtime exception, or in the worst case result in a crash. Silently giving bad results is one of the worst categories of bugs, and we are intending to fix such issues with the highest priority.

话虽如此，有时情况还是超出了我们的控制范围，尤其是涉及驱动程序甚至是硬件缺陷时(尽管在当今，这种情况很少见，除非有人从事将硬件推超出其出厂建议的操作范围) 条件，即超频").

Having said that, sometimes the things are outside of our control, especially when it comes to drivers or even hardware defects (although the latter are nowadays uncommon unless one engages in pushing the hardware outside of its factory recommended operating conditions, "overclocking").

不容小The的做法是在功能和压力测试方面全面投入生产之前，先对软件进行严格的测试.这种方法不仅应该发现实施方面的问题，还应发现底层系统的问题， 到硬件级别.

The practice that cannot be underestimated is to rigorously test the software before rolling out to production in both functional and stress testing aspects. This approach should not only uncover issues with the implementation, but with the underlying system, down to the hardware level, as well.

这篇关于C ++ AMP:什么时候lambda可能会错误地正确执行?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！