| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Remove the concept of word_size since it is meaningless in some
architectures. This is also done in preparation to possibly introduce
8-byte aligned messages.
Message-Id: <Y+lkv0uMo/3+hbCb@jupiter.tail36e24.ts.net>
|
| |
|
|
| |
Message-Id: <Y3/Z1CGL8D4OwT66@viriathus>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Basic syntax is presented below and allows users to define
nested structured types by using simpler or structure types as
members. Mig will use the C padding and alignment rules to produce
the same size as the corresponding C structures.
type timespec_t = struct {
uint32_t tv_sec;
uint32_t tv_nsec;
};
This allows us to build stubs that are more easily adaptable to other
architectures.
Message-Id: <Y2SjQSMOINY8I5Dy@viriathus>
|
| |
|
|
|
|
|
|
|
| |
This is only done when data is inlined with a concrete size. It
ensures the C and Mig types have the same size in the target arch.
Tested by building the hurd package. No assertions were triggered.
Message-Id: <YekIQaxvs+4FrHyw@viriathus>
|
| |
|
|
|
| |
Although in practice the buffers can be modified since they are from the
message, it leads to missing const where it would otherwise make sense.
|
| |
|
