Displaying 18 results from an estimated 18 matches for "__v".
Did you mean:
__va
2007 Aug 20
2
SSE bug on Win32 with GCC 4.2.1
Jean-Marc Valin wrote:
>> I recently found a .. weird bug on Win32 SSE with GCC 4.2.1.
>>
>> In libspeex/cb_search_sse.h, the following union is used:
>>
>> union {
>> float __a[4];
>> __m128 __v;
>> } __u;
>>
>> For some odd reason, this particular version of GCC will not 16-byte
>> align the union. IE; the alignment requirement of __v isn't propagated.
>> Changing it into this:
>>
>> union {
>> float __a[4];
>> __m128 __v;...
2016 Apr 13
0
[PATCH 1/1] x32 support
...---------------------------------- */
+
+/*
+ * sys/io.h for the x32 architecture
+ *
+ * Basic I/O macros
+ */
+
+#ifndef _SYS_IO_H
+#define _SYS_IO_H 1
+
+/* I/O-related system calls */
+
+int iopl(int);
+int ioperm(__u64, __u64, int);
+
+/* Basic I/O macros */
+
+static __inline__ void outb(__u8 __v, __u16 __p)
+{
+ asm volatile ("outb %0,%1" : : "a" (__v), "dN"(__p));
+}
+
+static __inline__ void outw(__u16 __v, __u16 __p)
+{
+ asm volatile ("outw %0,%1" : : "a" (__v), "dN"(__p));
+}
+
+static __inline__ void outl(__u32 __v, __u16 __...
2007 Aug 20
3
SSE bug on Win32 with GCC 4.2.1
...t isn't spam) or label
similar future email. If you have any questions, see
the administrator of that system for details.
Content preview: I recently found a .. weird bug on Win32 SSE with GCC 4.2.1.
In libspeex/cb_search_sse.h, the following union is used: union { float __a[4];
__m128 __v; } __u; [...]
Content analysis details: (4.0 points, 3.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
0.0 BAYES_50 BODY: Bayesian spam probability is 40 to 60%
[score:...
2006 Jun 26
0
[klibc 37/43] x86_64 support for klibc
...-------- */
+
+/*
+ * sys/io.h for the i386 architecture
+ *
+ * Basic I/O macros
+ */
+
+#ifndef _SYS_IO_H
+#define _SYS_IO_H 1
+
+/* I/O-related system calls */
+
+int iopl(int);
+int ioperm(unsigned long, unsigned long, int);
+
+/* Basic I/O macros */
+
+static __inline__ void outb(unsigned char __v, unsigned short __p)
+{
+ asm volatile ("outb %0,%1" : : "a" (__v), "dN"(__p));
+}
+
+static __inline__ void outw(unsigned short __v, unsigned short __p)
+{
+ asm volatile ("outw %0,%1" : : "a" (__v), "dN"(__p));
+}
+
+static __inline__ vo...
2006 Jun 26
0
[klibc 24/43] i386 support for klibc
...-------- */
+
+/*
+ * sys/io.h for the i386 architecture
+ *
+ * Basic I/O macros
+ */
+
+#ifndef _SYS_IO_H
+#define _SYS_IO_H 1
+
+/* I/O-related system calls */
+
+int iopl(int);
+int ioperm(unsigned long, unsigned long, int);
+
+/* Basic I/O macros */
+
+static __inline__ void outb(unsigned char __v, unsigned short __p)
+{
+ asm volatile ("outb %0,%1" : : "a" (__v), "dN" (__p));
+}
+
+static __inline__ void outw(unsigned short __v, unsigned short __p)
+{
+ asm volatile ("outw %0,%1" : : "a" (__v), "dN" (__p));
+}
+
+static __inline__...
2007 Aug 22
0
SSE bug on Win32 with GCC 4.2.1
...gt; Jean-Marc Valin wrote:
>>>> I recently found a .. weird bug on Win32 SSE with GCC 4.2.1.
>>>>
>>>> In libspeex/cb_search_sse.h, the following union is used:
>>>>
>>>> union {
>>>> float __a[4];
>>>> __m128 __v;
>>>> } __u;
>>>>
>>>> For some odd reason, this particular version of GCC will not 16-byte
>>>> align the union. IE; the alignment requirement of __v isn't propagated.
>>>> Changing it into this:
>>>>
>>>> un...
2004 Jan 24
1
get rid of various warnings, errors in io.h
In 0.97 io.h is wrong in several places.
it should be returning __v, not v.
static __inline__ unsigned char
inb(unsigned short __p)
{
unsigned char __v;
asm volatile("inb %1,%0" : "=a" (__v) : "dN" (__p));
return v;
}
How do I get rid of these warnings?
/home/mesa/boot/klibc/klibc/include/stdlib.h:21: warning: shadowing built...
2007 Aug 22
1
SSE bug on Win32 with GCC 4.2.1
...com> wrote:
>
> Jean-Marc Valin wrote:
> >> I recently found a .. weird bug on Win32 SSE with GCC 4.2.1.
> >>
> >> In libspeex/cb_search_sse.h, the following union is used:
> >>
> >> union {
> >> float __a[4];
> >> __m128 __v;
> >> } __u;
> >>
> >> For some odd reason, this particular version of GCC will not 16-byte
> >> align the union. IE; the alignment requirement of __v isn't propagated.
> >> Changing it into this:
> >>
> >> union {
> >>...
2009 Nov 05
1
virtio: Add memory statistics reporting to the balloon driver
agl at linux.vnet.ibm.com wrote:
> Here are the corresponding changes to the Linux virtio driver...
>
> virtio: Add memory statistics reporting to the balloon driver
>
> When using ballooning to manage overcommitted memory on a host, a system for
> guests to communicate their memory usage to the host can provide information
> that will minimize the impact
2009 Nov 05
1
virtio: Add memory statistics reporting to the balloon driver
agl at linux.vnet.ibm.com wrote:
> Here are the corresponding changes to the Linux virtio driver...
>
> virtio: Add memory statistics reporting to the balloon driver
>
> When using ballooning to manage overcommitted memory on a host, a system for
> guests to communicate their memory usage to the host can provide information
> that will minimize the impact
2005 Jul 11
1
Compile Error chan_sccp-20050705 on asterisk 1.0.9 (tarball)
...ctions.c:765: request for member `sin_port' in something not a structure or union
sccp_actions.c:765: request for member `sin_port' in something not a structure or union
sccp_actions.c:765: request for member `sin_port' in something not a structure or union
sccp_actions.c:759: warning: `__v' might be used uninitialized in this function
sccp_actions.c:765: warning: `__v' might be used uninitialized in this function
sccp_actions.c: In function `sccp_handle_forward_stat_req':
sccp_actions.c:838: parse error before `*'
sccp_actions.c:839: `r1' undeclared (first use in...
2006 Jun 28
35
[klibc 00/31] klibc as a historyless patchset (updated and reorganized)
I have updated the klibc patchset based on feedback received. In
particular, the patchset has been reorganized so as not to break
git-bisect.
Additionally, this updates the patch base to 2.6.17-git12
(d38b69689c349f35502b92e20dafb30c62d49d63) and klibc 1.4.8; the main
difference on the klibc side is removal of obsolete code.
This is also available as a git tree at:
2020 Jun 30
0
[PATCH 02/18] compiler.h: Split {READ, WRITE}_ONCE definitions out into rwonce.h
...red ordering.
- */
-#include <asm/barrier.h>
-#include <linux/kasan-checks.h>
-#include <linux/kcsan-checks.h>
-
/**
* data_race - mark an expression as containing intentional data races
*
@@ -272,65 +250,6 @@ void ftrace_likely_update(struct ftrace_likely_data *f, int val,
__v; \
})
-/*
- * Use __READ_ONCE() instead of READ_ONCE() if you do not require any
- * atomicity or dependency ordering guarantees. Note that this may result
- * in tears!
- */
-#define __READ_ONCE(x) (*(const volatile __unqual_scalar_typeof(x) *)&(x))
-
-#define __READ_ONCE_SCALAR(x)...
2020 Jul 10
0
[PATCH v3 02/19] compiler.h: Split {READ, WRITE}_ONCE definitions out into rwonce.h
...red ordering.
- */
-#include <asm/barrier.h>
-#include <linux/kasan-checks.h>
-#include <linux/kcsan-checks.h>
-
/**
* data_race - mark an expression as containing intentional data races
*
@@ -272,65 +250,6 @@ void ftrace_likely_update(struct ftrace_likely_data *f, int val,
__v; \
})
-/*
- * Use __READ_ONCE() instead of READ_ONCE() if you do not require any
- * atomicity or dependency ordering guarantees. Note that this may result
- * in tears!
- */
-#define __READ_ONCE(x) (*(const volatile __unqual_scalar_typeof(x) *)&(x))
-
-#define __READ_ONCE_SCALAR(x)...
2014 Nov 03
8
[LLVMdev] [PATCH] Protection against stack-based memory corruption errors using SafeStack
...;ir"
+# endif
+#elif defined(__x86_64__)
+# define MOVPTR "movq"
+# define IMM_MODE "nr"
+#endif
+
+#if defined(__linux__) && (defined(__i386__) || defined(__x86_64__))
+
+# define __THREAD_GETMEM_L(offset) \
+ __extension__ ({ unsigned long __v; \
+ asm volatile (MOVPTR " %%fs:%P1,%q0" \
+ : "=r" (__v) : "i" (offset)); __v; })
+
+# define __THREAD_SETMEM_L(offset, value) \
+ asm volatile (MOVPTR " %q0,%%fs:%P1" :...
2020 Jul 10
24
[PATCH 00/18] Allow architectures to override __READ_ONCE()
Hi all,
This is version three of the patches I previously posted here:
v1: https://lore.kernel.org/lkml/20191108170120.22331-1-will at kernel.org/
v2: https://lore.kernel.org/r/20200630173734.14057-1-will at kernel.org
Changes since v2 include:
* Actually add the barrier in READ_ONCE() for Alpha!
* Implement Alpha's smp_load_acquire() using __READ_ONCE(), rather than
the other
2020 Jun 30
32
[PATCH 00/18] Allow architectures to override __READ_ONCE()
Hi everyone,
This is the long-awaited version two of the patches I previously
posted in November last year:
https://lore.kernel.org/lkml/20191108170120.22331-1-will at kernel.org/
I ended up parking the series while the READ_ONCE() implementation was
being overhauled, but with that merged during the recent merge window
and LTO patches being posted again [1], it was time for a refresh.
The
2020 Jun 30
32
[PATCH 00/18] Allow architectures to override __READ_ONCE()
Hi everyone,
This is the long-awaited version two of the patches I previously
posted in November last year:
https://lore.kernel.org/lkml/20191108170120.22331-1-will at kernel.org/
I ended up parking the series while the READ_ONCE() implementation was
being overhauled, but with that merged during the recent merge window
and LTO patches being posted again [1], it was time for a refresh.
The