Fix: Field types native byte order refers to the trace
authorJérémie Galarneau <jeremie.galarneau@efficios.com>
Wed, 4 Feb 2015 20:38:06 +0000 (15:38 -0500)
committerJérémie Galarneau <jeremie.galarneau@efficios.com>
Wed, 4 Feb 2015 20:38:06 +0000 (15:38 -0500)
commitc35a1669cedba73681bd259ea7945aa55643e158
treef2f172d883f4904b4ef15e6d46ce70ba56876c08
parenta847c172f75ef6fe905c889866aedfbf75230769
Fix: Field types native byte order refers to the trace

Following a misunderstanding of the CTF specification, the native
byte order was implemented as meaning the host's endianness. It should
refer to the Trace's endianness.

This modification ensures that stream classes, event classes and field
types correctly inherit the trace's endianness when "native" is used.

Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>
13 files changed:
bindings/python/babeltrace.i.in
formats/ctf/ir/event-types.c
formats/ctf/ir/event.c
formats/ctf/ir/stream-class.c
formats/ctf/ir/trace.c
include/babeltrace/ctf-ir/event-internal.h
include/babeltrace/ctf-ir/event-types-internal.h
include/babeltrace/ctf-ir/event-types.h
include/babeltrace/ctf-ir/stream-class-internal.h
include/babeltrace/ctf-ir/trace-internal.h
include/babeltrace/ctf-ir/trace.h
include/babeltrace/ctf-writer/writer.h
include/babeltrace/types.h
This page took 0.026006 seconds and 4 git commands to generate.