On 02/09/14 14:54, Luca Barbato wrote:
> We could, I need to try not-last-commit clang and see if they botch that
> the same way.
Ok, looks like 3.4 is as naive as you'd expect for an early backend.
We can drop the override since at least gcc 4.7 and 4.8 do what we
expect or keep it mentioning "c
On 02/09/14 12:12, Janne Grunau wrote:
> On 2014-09-02 03:24:34 +0200, Luca Barbato wrote:
>> ---
>>
>> Now with better names.
>
> thanks
>
>> libavutil/ppc/intreadwrite.h | 64
>> +++-
>> 1 file changed, 40 insertions(+), 24 deletions(-)
>>
>> diff --gi
On 2014-09-02 03:24:34 +0200, Luca Barbato wrote:
> ---
>
> Now with better names.
thanks
> libavutil/ppc/intreadwrite.h | 64
> +++-
> 1 file changed, 40 insertions(+), 24 deletions(-)
>
> diff --git a/libavutil/ppc/intreadwrite.h b/libavutil/ppc/intr
---
Now with better names.
libavutil/ppc/intreadwrite.h | 64 +++-
1 file changed, 40 insertions(+), 24 deletions(-)
diff --git a/libavutil/ppc/intreadwrite.h b/libavutil/ppc/intreadwrite.h
index fec54e6..4471c6a 100644
--- a/libavutil/ppc/intreadwrite.h
On 2014-08-30 22:04:34 +0200, Luca Barbato wrote:
> ---
>
> Now with less typos and possibly working. (I'll try to test it later)
>
> libavutil/ppc/intreadwrite.h | 66
>
> 1 file changed, 42 insertions(+), 24 deletions(-)
>
> diff --git a/libavutil
---
Now with less typos and possibly working. (I'll try to test it later)
libavutil/ppc/intreadwrite.h | 66
1 file changed, 42 insertions(+), 24 deletions(-)
diff --git a/libavutil/ppc/intreadwrite.h b/libavutil/ppc/intreadwrite.h
index fec54e6..4bb
On 30/08/14 20:48, Timothy Gu wrote:
> On Aug 30, 2014 6:32 AM, "Luca Barbato" wrote:
>>
>> ---
>>
>> I tested with recent compilers and the problem mentioned is actual only
>> for -O0.
>>
>> libavutil/ppc/intreadwrite.h | 48
> ++--
>> 1 file changed, 33 i
On Aug 30, 2014 6:32 AM, "Luca Barbato" wrote:
>
> ---
>
> I tested with recent compilers and the problem mentioned is actual only
> for -O0.
>
> libavutil/ppc/intreadwrite.h | 48
++--
> 1 file changed, 33 insertions(+), 15 deletions(-)
>
> diff --git a/li
On 30/08/14 15:32, Luca Barbato wrote:
> ---
>
> I tested with recent compilers and the problem mentioned is actual only
> for -O0.
>
Actually clang-3.4 seems having problems as well.
lu
___
libav-devel mailing list
libav-devel@libav.org
https://list
---
I tested with recent compilers and the problem mentioned is actual only
for -O0.
libavutil/ppc/intreadwrite.h | 48 ++--
1 file changed, 33 insertions(+), 15 deletions(-)
diff --git a/libavutil/ppc/intreadwrite.h b/libavutil/ppc/intreadwrite.h
index f
On 29/08/14 01:38, Timothy Gu wrote:
> The above looks correct. However
>
> #define AV_RB64(p) (*(const uint64_t *)(p))
> #define AV_WB64(p, v) (*(uint64_t *)(p) = (v))
>
> below will need to be guarded with HAVE_BIGENDIAN.
Possibly tested that gcc nowadays works as should and removed.
lu
On Aug 28, 2014 4:22 PM, "Luca Barbato" wrote:
>
> ---
>
> should fix the problem reported on irc on ppc64le, tomorrow hopefully will
> be tested.
>
> libavutil/ppc/intreadwrite.h | 22 +++---
> 1 file changed, 15 insertions(+), 7 deletions(-)
>
> diff --git a/libavutil/ppc/intrea
---
should fix the problem reported on irc on ppc64le, tomorrow hopefully will
be tested.
libavutil/ppc/intreadwrite.h | 22 +++---
1 file changed, 15 insertions(+), 7 deletions(-)
diff --git a/libavutil/ppc/intreadwrite.h b/libavutil/ppc/intreadwrite.h
index fec54e6..f5c3022 10
13 matches
Mail list logo
