History log of /seL4-test-master/tools/nanopb/tests/encode_unittests/encode_unittests.c
Revision Date Author Comments
# 6a595279 01-Dec-2018 Petteri Aimonen <jpa@git.mail.kapsi.fi>

New field descriptor format.

Now field information is stored as a variable-length uint32_t array.
This reduces the minimum size in most cases:

old new
basic field: 10 bytes 4 bytes
repeated field: 10 bytes 8 bytes
field with 12bit tag/size: 16 bytes 8 bytes
field with 16bit tag/size: 16 bytes 16 bytes
field with 32bit tag/size: 28 bytes 16 bytes

Further, now the descriptor size can be increased per-field and per-message,
instead of previous global PB_FIELD_16BIT and PB_FIELD_32BIT.

PB_FIELD_32BIT still affects the pb_size_t type, which is 16-bit by default.


# 2210cd92 12-Nov-2018 Petteri Aimonen <jpa@git.mail.kapsi.fi>

Big refactoring to better separate field descriptor encoding from logic.

This will enable further development of the field descriptor encoding.


# c59a9d7e 04-May-2017 Petteri Aimonen <jpa@git.mail.kapsi.fi>

Combine pb_encode_varint32() into pb_encode_varint()


# bee8e20e 02-May-2017 Petteri Aimonen <jpa@git.mail.kapsi.fi>

Unit test updates for the string length


# f7013275 01-May-2017 Alice Wang <aw@squareup.com>

unit test fix for checking string encoding length


# 4b3b4b1b 15-Mar-2017 Nick Ewalt <nicholasewalt@google.com>

Add pb_encode_varint32 and pb_encode_svarint32

- Optimized 32 bit versions of pb_encode_varint and pb_encode_svarint


# 38613acd 07-Sep-2014 Petteri Aimonen <jpa@git.mail.kapsi.fi>

Add a few missing unit tests


# 1dd9f190 18-Aug-2014 Petteri Aimonen <jpa@git.mail.kapsi.fi>

Change the _count fields to use pb_size_t datatype.

Update issue 82
Status: FixedInGit


# a641e21b 09-Aug-2014 Petteri Aimonen <jpa@git.mail.kapsi.fi>

Separate field iterator logic from pb_decode to pb_common.


# b63e582b 05-Apr-2014 Petteri Aimonen <jpa@git.mail.kapsi.fi>

Add a convenience function pb_get_encoded_size()

There is minimal size penalty from this, and it is probably much more
intuitive to use than PB_OSTREAM_SIZING itself.

This has been suggested before also, but I ended up refusing it back
them. Reconsidering it now, I see that an intuitive API is much better
than any amount of documentation explaining a non-intuitive API.

Update issue 16
Status: FixedInGit


# 28720784 29-Oct-2013 Petteri Aimonen <jpa@git.mail.kapsi.fi>

Remove the NANOPB_INTERNALS functions from public API.

These have been deprecated since nanopb-0.1.6 (some since 0.1.3).
Equivalent functions with better interface are available in the API.

Update issue 91
Status: FixedInGit


# ed564186 24-Oct-2013 Petteri Aimonen <jpa@git.mail.kapsi.fi>

Detect invalid sizes when encoding bytes fields.


# e83fbd18 20-Oct-2013 Petteri Aimonen <jpa@git.mail.kapsi.fi>

Check array max size when encoding.

Update issue 90
Status: FixedInGit


# 388d4de8 26-Sep-2013 Petteri Aimonen <jpa@git.mail.kapsi.fi>

Add #defines for the maximum encoded message size.

Update issue 89
Status: FixedInGit


# 262c6267 08-Sep-2013 Petteri Aimonen <jpa@git.mail.kapsi.fi>

Start moving the tests into subfolders. Transition to SCons for build system for the tests.

Only a few tests updated so far. Have to include all the rest before merging to mainline.

Update issue 63
Status: Started