search for: _le

On Tue, May 17, 2016 at 03:41:10PM +0200, Pino Toscano wrote: > +extern bool guestfs_int_version_is (const struct version *v, int maj, int min, int mic); I think calling this function "is" is a bit misleading. I think we should have _ge and _le functions (cf my patch). This comparison for example is wrong: > /* qemu 1.1 claims to support virtio-scsi but in reality it's broken. */ > - if (data->qemu_version_major == 1 && data->qemu_version_minor < 2) > + if (!guestfs_int_version_is (&data->qemu_v...

Ok here's another one: player_example.c: In function `open_audio': player_example.c:138: `AFMT_S16_NE' undeclared (first use in this function) It worked fine once I switched it from _NE to _LE, this code will help portability: #if defined(__FreeBSD__) # define AFMT_S16_NE AFMT_S16_LE #elif defined(_AIX) || defined(AIX) # define AFMT_S16_NE AFMT_S16_BE #endif I'm not sure what other OS's may also require this be defined.. --- >8 ---- List archives: http://www.xiph.org/arc...

...tentially write code that detected endiannes at runtime and chose > multiversioned code based on that, but that is ugly and optimization > prohibiting). > Why not add types with explicit endianess? A trick I use for reading binary files across platforms is to define the types int32, int32_le and int32_be : int32 is platform-native, _le and _be are little and big endian, respectively. I use and #ifdef in my types.hpp to determine which of _le and _be is a typedef for the standard uint32, and the other is implemented as a class with operator int32(). "add i32_be %X, 8" looks el...

On Mon, Sep 29, 2008 at 8:18 AM, Christian Plessl <christian.plessl at uni-paderborn.de> wrote: > - Is the architecture dependence of LLVM IR only an artifact of llvm- > gcc producing architecture dependent results? No. It also is an artifact of code compiling architecture and OS dependent features based on what they detect at configure time It is an artifact of compiling non-type

On 29.09.2008, at 11:53, Jonathan S. Shapiro wrote: > Watching this thread, it occurs to me that the "V" in "LLVM" is > creating > confusion. So far as I know, LLVM is the first project to use > "virtual" > to refer to the instruction set of the intermediate form. I understand > why this labeling made sense (sort of), but it was unfortunate. The

...W.M. Jones wrote: > On Tue, May 17, 2016 at 03:41:10PM +0200, Pino Toscano wrote: > > +extern bool guestfs_int_version_is (const struct version *v, int maj, int min, int mic); > > I think calling this function "is" is a bit misleading. I think > we should have _ge and _le functions (cf my patch). Makes sense, renamed to _ge. > This comparison for example is wrong: > > > /* qemu 1.1 claims to support virtio-scsi but in reality it's broken. */ > > - if (data->qemu_version_major == 1 && data->qemu_version_minor < 2) > &g...

...which disapear when member server (powered by samba and winbind) can't discuss (for network resaon : i.e. link is down for 10 mn) with ADC (Domain controler) which is located on main site. Is this a known issue of samba/winbind ? How can we fix this issue. Thank you for your support. -- _LE DUF' AKA DEMY_ Site : http://www.ledufakademy.fr Mail : public at ledufakademy.fr

The nouveau driver makes a number of unaligned accesses via the ROM16(), ROM32() and ROM64() macros which fault on SPARC (but would be transparently handled by x86 hardware). Making use of get_unaligned() macro fixes the problem for me. diff --git a/drivers/gpu/drm/nouveau/nouveau_bios.h b/drivers/gpu/drm/nouveau/nouveau_bios.h index 7ccd28f..92031f6 100644 ---

Hi, this adds an helper version struct, and uses it in the backends (for the libvirt and qemu versions) and inspection code. This also moves common code to that, so it is not repeated in many places. This should help with the small refactoring proposed with https://www.redhat.com/archives/libguestfs/2016-May/msg00070.html Thanks, Pino Toscano (2): src: start unifying version handling