search for: is_signed

...s=c,c++ --disable-multilib when I run: $ make I get the following errors: /home/draikes/src/llvm/include/llvm/ADT/StringRef.h:346:19: error: â EURO ~enable_ifâ EURO (tm) in namespace â EURO ~stdâ EURO (tm) does not name a template type typename std::enable_if<std::numeric_limits<T>::is_signed, bool>::type ^ /home/draikes/src/llvm/include/llvm/ADT/StringRef.h:346:28: error: expected unqualified-id before â EURO ~<â EURO (tm) token typename std::enable_if<std::numeric_limits<T>::is_signed, bool>::type ^ /home/draikes/sr...

Continuing with problems that I've uncovered while getting pqR to work on Windows... The file src/ghuwin32/psignal.c (used only in Windows builds) fails to use the sigset_t type in all places where it should, using "int" some places instead. Here is a diff of the needed corrections: @@ -253,7 +253,7 @@ sighandler_t signal(int signal_Number, sighandler_t signal_Handler) int

op 19-05-14 14:30, Christian K?nig schreef: > Am 19.05.2014 12:10, schrieb Maarten Lankhorst: >> op 19-05-14 10:27, Christian K?nig schreef: >>> Am 19.05.2014 10:00, schrieb Maarten Lankhorst: >>> [SNIP] >>> The problem here is that the whole approach collides with the way we do reset handling from a conceptual point of view. Every IOCTL or other call chain into

Am 19.05.2014 12:10, schrieb Maarten Lankhorst: > op 19-05-14 10:27, Christian K?nig schreef: >> Am 19.05.2014 10:00, schrieb Maarten Lankhorst: >> [SNIP] >> The problem here is that the whole approach collides with the way we >> do reset handling from a conceptual point of view. Every IOCTL or >> other call chain into the driver is protected by the read side of

op 22-07-14 15:45, Christian K?nig schreef: > Am 22.07.2014 15:26, schrieb Daniel Vetter: >> On Tue, Jul 22, 2014 at 02:19:57PM +0200, Christian K?nig wrote: >>> Am 22.07.2014 13:57, schrieb Daniel Vetter: >>>> On Tue, Jul 22, 2014 at 01:46:07PM +0200, Daniel Vetter wrote: >>>>> On Tue, Jul 22, 2014 at 10:43:13AM +0200, Christian K?nig wrote:

Am 19.05.2014 10:00, schrieb Maarten Lankhorst: > op 15-05-14 18:13, Christian K?nig schreef: >> Am 15.05.2014 17:58, schrieb Maarten Lankhorst: >>> op 15-05-14 17:48, Christian K?nig schreef: >>>> Am 15.05.2014 16:18, schrieb Maarten Lankhorst: >>>>> op 15-05-14 15:19, Christian K?nig schreef: >>>>>> Am 15.05.2014 15:04, schrieb

op 19-05-14 10:27, Christian K?nig schreef: > Am 19.05.2014 10:00, schrieb Maarten Lankhorst: >> op 15-05-14 18:13, Christian K?nig schreef: >>> Am 15.05.2014 17:58, schrieb Maarten Lankhorst: >>>> op 15-05-14 17:48, Christian K?nig schreef: >>>>> Am 15.05.2014 16:18, schrieb Maarten Lankhorst: >>>>>> op 15-05-14 15:19, Christian K?nig

Hey, op 22-07-14 17:02, Christian K?nig schreef: > Am 22.07.2014 16:44, schrieb Maarten Lankhorst: >> op 22-07-14 15:45, Christian K?nig schreef: >>> Am 22.07.2014 15:26, schrieb Daniel Vetter: >>>> On Tue, Jul 22, 2014 at 02:19:57PM +0200, Christian K?nig wrote: >>>>> Am 22.07.2014 13:57, schrieb Daniel Vetter: >>>>>> On Tue, Jul 22,

op 22-07-14 17:59, Christian K?nig schreef: > Am 22.07.2014 17:42, schrieb Daniel Vetter: >> On Tue, Jul 22, 2014 at 5:35 PM, Christian K?nig >> <christian.koenig at amd.com> wrote: >>> Drivers exporting fences need to provide a fence->signaled and a fence->wait >>> function, everything else like fence->enable_signaling or calling >>>

Am 22.07.2014 16:44, schrieb Maarten Lankhorst: > op 22-07-14 15:45, Christian K?nig schreef: >> Am 22.07.2014 15:26, schrieb Daniel Vetter: >>> On Tue, Jul 22, 2014 at 02:19:57PM +0200, Christian K?nig wrote: >>>> Am 22.07.2014 13:57, schrieb Daniel Vetter: >>>>> On Tue, Jul 22, 2014 at 01:46:07PM +0200, Daniel Vetter wrote: >>>>>> On

op 15-05-14 18:13, Christian K?nig schreef: > Am 15.05.2014 17:58, schrieb Maarten Lankhorst: >> op 15-05-14 17:48, Christian K?nig schreef: >>> Am 15.05.2014 16:18, schrieb Maarten Lankhorst: >>>> op 15-05-14 15:19, Christian K?nig schreef: >>>>> Am 15.05.2014 15:04, schrieb Maarten Lankhorst: >>>>>> op 15-05-14 11:42, Christian K?nig

Am 15.05.2014 17:58, schrieb Maarten Lankhorst: > op 15-05-14 17:48, Christian K?nig schreef: >> Am 15.05.2014 16:18, schrieb Maarten Lankhorst: >>> op 15-05-14 15:19, Christian K?nig schreef: >>>> Am 15.05.2014 15:04, schrieb Maarten Lankhorst: >>>>> op 15-05-14 11:42, Christian K?nig schreef: >>>>>> Am 15.05.2014 11:38, schrieb

Am 23.07.2014 08:40, schrieb Maarten Lankhorst: > op 22-07-14 17:59, Christian K?nig schreef: >> Am 22.07.2014 17:42, schrieb Daniel Vetter: >>> On Tue, Jul 22, 2014 at 5:35 PM, Christian K?nig >>> <christian.koenig at amd.com> wrote: >>>> Drivers exporting fences need to provide a fence->signaled and a fence->wait >>>> function,

Am 22.07.2014 17:42, schrieb Daniel Vetter: > On Tue, Jul 22, 2014 at 5:35 PM, Christian K?nig > <christian.koenig at amd.com> wrote: >> Drivers exporting fences need to provide a fence->signaled and a fence->wait >> function, everything else like fence->enable_signaling or calling >> fence_signaled() from the driver is optional. >> >> Drivers

Am 19.05.2014 15:35, schrieb Maarten Lankhorst: > op 19-05-14 14:30, Christian K?nig schreef: >> Am 19.05.2014 12:10, schrieb Maarten Lankhorst: >>> op 19-05-14 10:27, Christian K?nig schreef: >>>> Am 19.05.2014 10:00, schrieb Maarten Lankhorst: >>>> [SNIP] >>>> The problem here is that the whole approach collides with the way >>>>

On Tue, Jul 22, 2014 at 02:19:57PM +0200, Christian K?nig wrote: > Am 22.07.2014 13:57, schrieb Daniel Vetter: > >On Tue, Jul 22, 2014 at 01:46:07PM +0200, Daniel Vetter wrote: > >>On Tue, Jul 22, 2014 at 10:43:13AM +0200, Christian K?nig wrote: > >>>Am 22.07.2014 06:05, schrieb Dave Airlie: > >>>>On 9 July 2014 22:29, Maarten Lankhorst