On Fri, Feb 25, 2011 at 12:43 AM, Corentin Chary
wrote:
>> Is there a special reason why you use __always_inline
>> instead of inline in bitops.h?
>
> Because it's not only a hint, I really want this function to be inlined.
I applied a patch which changes this to just inline. See osdep.h.
On Fri, Feb 25, 2011 at 12:43 AM, Corentin Chary
wrote:
>> Is there a special reason why you use __always_inline
>> instead of inline in bitops.h?
>
> Because it's not only a hint, I really want this function to be inlined.
>
>> This breaks compilation for mingw :-(
>>
>> mingw also fails at timer
> Is there a special reason why you use __always_inline
> instead of inline in bitops.h?
Because it's not only a hint, I really want this function to be inlined.
> This breaks compilation for mingw :-(
>
> mingw also fails at timersub() in vnc.c.
Then we should defined timersub when not availabl
Am 24.02.2011 22:03, schrieb Stefan Weil:
Am 04.02.2011 09:05, schrieb Corentin Chary:
From: Corentin Chary
Hi,
Since v2:
- Fixed some styles issues
- Rebased to current master
- Fixed a Makefile issue (using .c instead of .o)
I rebased the series against current master, it contains:
- Adap
Am 04.02.2011 09:05, schrieb Corentin Chary:
From: Corentin Chary
Hi,
Since v2:
- Fixed some styles issues
- Rebased to current master
- Fixed a Makefile issue (using .c instead of .o)
I rebased the series against current master, it contains:
- Adaptive Tight Encoding: send lossy or lossless
From: Corentin Chary
Hi,
Since v2:
- Fixed some styles issues
- Rebased to current master
- Fixed a Makefile issue (using .c instead of .o)
I rebased the series against current master, it contains:
- Adaptive Tight Encoding: send lossy or lossless updates depending on the
update frequency of
