Re: [x265] Negative integer shifts

2017-04-26 Thread Mario *LigH* Rohkrämer
Hi. Ma0 already submitted a patch on April 20th, which handles this issue by casting them to unsigned. I guess it was not yet committed. By the way, Multicoreware prefers patches in plain text in the message body for easier review. Am 26.04.2017, 16:54 Uhr, schrieb Andrey Semashev :

[x265] Negative integer shifts

2017-04-26 Thread Andrey Semashev
Hi, While compiling 2.4 I'm seeind lots of warnings like this: .../source/common/ipfilter.cpp: In instantiation of ‘void {anonymous}::interp_horiz_ps_c(const pixel*, intptr_t, int16_t*, intptr_t, int, int) [with int N = 8; int width = 4; int height = 4; pixel = unsigned char; intptr_t = long

Re: [x265] [PATCH] cmake: switch to c++11 for Clang and GCC

2017-04-26 Thread Mateusz Brzostek
I will make speed test -std=c++11 vs. -std=gnu++11 (in the night) and if x265 build with GCC -std=c++11 is not slower than with -std=gnu++11 I will be convinced to -std=c++11. W dniu 2017-04-26 o 08:07, Michael Lackner pisze: > Actually, I compiled x265 2.4+2 just yesterday using GCC 6.2.0 on L