Nagy Mostafa
Nagy Mostafa
Revisited here too: [308](https://github.com/tc39/ecmascript_simd/issues/308) The polyfill should be fixed to follow the spec.
Seems the consensus here is to have neg for both sign/unsigned ? Polyfill/tests still need to be fixed.
I think it should still be left for Phase 2, not in favor of rushing it. And certainly we can start working on a draft spec for phase 2.
I agree that using Number.prototype.ToString() is the right answer, and after a closer look at the spec, I think that's the intent: ``` Let elements be CreateArrayFromList(argument.[[SIMDElements]]). Let t be...
Yes. I think just adding a note under [[SIMDElements]] definition indicating that values are either Number or Booleans depending on the SIMDTypeDescriptor should be enough. I will submit a PR.
I am in favor of removing them from SIMD.js, since their semantics doesn't serve any purpose now (neither JS or IEEE compliant). We can add them to WASM after semantics...
@ftynse, that means we have to define our own Std->LLVM lowering pass to configure the pattern, no ? Also, the same callback will have be used for all AllocOps in...
Declaring our own Allocation Op and the needed lowering pass to LLVM just seemed like an overkill for the simple need to rename the callback function (I would agree if...
The way I see it, there are two levels of semantics for an AllocOp. For std dialect, it just says get me some memory for a MemRef. The lower level...
Hi Mehdi, What is the call on this one ? I still believe that having some level of configuration for `AllocOp` is the way to go, and to serve as...