On 15/04/2014 06:00, Patrick Walton wrote:
I'm considering using 32-bit fixed-point (16 bits for the fraction, 16
bits for the integer portion) for percentages in CSS.
How should numbers (and dimensions and percentages) be represented in
the CSS parser? Do you still see performance benefits wh
On 4/16/14 1:11 AM, Simon Sapin wrote:
On 15/04/2014 06:00, Patrick Walton wrote:
Hi everyone,
I'm considering using 32-bit fixed-point (16 bits for the fraction, 16
bits for the integer portion) for percentages in CSS. The reason is that
we can use the following four SSE4/AVX instructions on x
On 15/04/2014 06:00, Patrick Walton wrote:
Hi everyone,
I'm considering using 32-bit fixed-point (16 bits for the fraction, 16
bits for the integer portion) for percentages in CSS. The reason is that
we can use the following four SSE4/AVX instructions on x86 to compute
two sides at once:
;
Right now rustc has no option to detect CPU features, and advanced
features must be enabled explicitly. It seems reasonable to start adding
some basic feature detection to rustc as needed.
On 04/15/2014 07:15 PM, Jack Moffitt wrote:
Assuming this is enough precision for layout, I'd like to see
Assuming this is enough precision for layout, I'd like to see neon
versions before we landed anything like this. Will the API a user sees
look the same? In other words, is the change localized to MaybeAuto's
implementation?
Also, speaking of these SIMD optimizations, does rustc have a compiler
fla
Hi everyone,
I'm considering using 32-bit fixed-point (16 bits for the fraction, 16
bits for the integer portion) for percentages in CSS. The reason is that
we can use the following four SSE4/AVX instructions on x86 to compute
two sides at once:
; xmm0 contains the style values (percentag
6 matches
Mail list logo
