[cfe-dev] [RFC] C++17 hardware constructive / destructive interference size

[James Y Knight via cfe-dev]

On Fri, May 25, 2018 at 5:30 PM JF Bastien <jfbastien at apple.com> wrote:

>
>
> On May 25, 2018, at 2:23 PM, James Y Knight <jyknight at google.com> wrote:
>
> My own employer doesn't make ABI stability promises for that code, and
> thus is fine with changing the value anytime it feels like. That's not a
> generically viable strategy for a value provided by the standard library.
>
> Additionally, before I sent that email, I looked at a number of the uses,
> and it appeared as though a great many could be easily modified to use a
> runtime-determined alignment.
>
>
> That would be useful feedback on the paper… prior to it getting into
> C++17. The committee’s POV voting the paper in was that having a constexpr
> value was something we wanted, and so that’s what we have. At this point in
> time I’d like to focus on implementing C++17 as it is, and / or filing DRs
> as required.
>

Sure. I'm not on the committee. Even if I was, I certainly don't know that
I would have identified the problem...

But now that it has been identified, there's a choice of what to do. And
not implementing the function (and presumably filing a DR saying so) is
seeming like a pretty reasonable option.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20180525/3e26b0b2/attachment.html>