search for: __nonnull

...maining); /* Get resolution of clock CLOCK_ID. */ extern int clock_getres (clockid_t __clock_id, struct timespec *__res) __THROW; /* Get current value of clock CLOCK_ID and store it in TP. */ extern int clock_gettime (clockid_t __clock_id, struct timespec *__tp) __THROW __nonnull((2)); /* Set clock CLOCK_ID to value TP. */ extern int clock_settime (clockid_t __clock_id, const struct timespec *__tp) __THROW __nonnull((2)); # else # ifdef __REDIRECT extern int __REDIRECT (nanosleep, (const struct timespec *__requested_time,...

...clude/pthread.h:452: error: ‘__cpuset’ was not declared in this scope /usr/include/pthread.h:452: error: initializer expression list treated as compound expression /usr/include/pthread.h:453: error: expected ‘,’ or ‘;’ before ‘__THROW’ /usr/include/pthread.h:467: error: expected initializer before ‘__nonnull’ /usr/include/pthread.h:485: error: ‘pthread_t’ was not declared in this scope /usr/include/pthread.h:713: error: expected initializer before ‘__THROW’ /usr/include/pthread.h:721: error: expected initializer before ‘__THROW’ /usr/include/pthread.h:725: error: expected initializer before ‘__THROW’ /...

...oesn't have to. It's fine if you guys don't want to change it. It may never be a problem with gcc. This is the definition of pthread_mutex_lock() in glibc. There aren't any magic hints that this invalidates memory: extern int pthread_mutex_lock (pthread_mutex_t *__mutex) __THROWNL __nonnull ((1)); THOWNL is attribute((nothrow)). -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20150225/1d46e029/attachment.html>

...if you guys don't want to change > it. It may never be a problem with gcc. > > This is the definition of pthread_mutex_lock() in glibc. There aren't any > magic hints that this invalidates memory: > > extern int pthread_mutex_lock (pthread_mutex_t *__mutex) > __THROWNL __nonnull ((1)); > > THOWNL is attribute((nothrow)). Hm, this is actually a little worrying. Maarten, thoughts? I would have assumed there'd be a __attribute__((some_magic_thing)) in there. -ilia

...tools] Error 2 The posix_memalign function is declared in /usr/include/stdlib.h (which is included in xenpaging.c): #ifdef __USE_XOPEN2K /* Allocate memory of SIZE bytes with an alignment of ALIGNMENT. */ extern int posix_memalign (void **__memptr, size_t __alignment, size_t __size) __THROW __nonnull ((1)); #endif So, I edit the Makefile in tools/xenpaging and add the line: CFLAGS += -D__USE_XOPEN2K However, when I recompile, I get the same error. There also seems to be another condition in stdlib.h that must be satisfied before the __USE_XOPEN2K one will be checked: #ifndef __need_malloc_an...

...to change >> it. It may never be a problem with gcc. >> >> This is the definition of pthread_mutex_lock() in glibc. There aren't any >> magic hints that this invalidates memory: >> >> extern int pthread_mutex_lock (pthread_mutex_t *__mutex) >> __THROWNL __nonnull ((1)); >> >> THOWNL is attribute((nothrow)). > > Hm, this is actually a little worrying. Maarten, thoughts? I would > have assumed there'd be a __attribute__((some_magic_thing)) in there. In general things don't get optimized across function calls, except in case of in...

So you're saying a compiler can optimize: > > - statement with memory access > - read memory barrier > - statement with memory access > > To drop the second statement? I would worry about your definition of > memory barrier then.. > This is tricky, but I think you're mixing up the general case with the actual code you have. In general, you are pointing to this