Displaying 2 results from an estimated 2 matches for "ulittle64_t".
Did you mean:
ulittle32_t
2017 Feb 19
5
RFC: Adding llvm::ThinStream
...nd without worrying about reference lifetime issues.
To re-iterate: *When using a ThinStreamReader, copies are the exception,
not the rule and for most implementations of ThinStream will never occur.*
Suppose you have a struct:
struct Header {
char Magic[48];
ulittle16_t A;
ulittle16_t B;
ulittle64_t C;
};
To read this using a `ThinStreamReader`, you would write this:
ThinStreamReader Reader(Stream);
const Header *H;
if (auto EC = Reader.readObject(H))
return EC;
and `ThinStreamReader` just reinterpret_casts the underlying bytes to your
structure. The same is true for null terminated stri...
2017 Feb 22
2
RFC: Adding llvm::ThinStream
...ues.
>
> To re-iterate: *When using a ThinStreamReader, copies are the exception,
> not the rule and for most implementations of ThinStream will never occur.*
> Suppose you have a struct:
>
> struct Header {
> char Magic[48];
> ulittle16_t A;
> ulittle16_t B;
> ulittle64_t C;
> };
>
> To read this using a `ThinStreamReader`, you would write this:
>
> ThinStreamReader Reader(Stream);
> const Header *H;
> if (auto EC = Reader.readObject(H))
> return EC;
>
> and `ThinStreamReader` just reinterpret_casts the underlying bytes to your
> s...