protobuf

Protocol Buffers - Google's data interchange format (grpc依赖) https://developers.google.com/protocol-buffers/

Tag: Branch: Tree: 7d3e2bd2c4

Josh Haberman 7d3e2bd2c4 Sync with 8 months of Google-internal development. Many things have changed and been simplified. The memory-management story for upb_def and upb_handlers is much more robust; upb_def and upb_handlers should be fairly stable interfaces now. There is still much work to do for the runtime component (upb_sink).		12 years ago
..
README	Sync from internal Google development.	13 years ago
error.c	Sync with 8 months of Google-internal development.	12 years ago
error.h	Sync from internal Google development.	13 years ago
io.c	Sync with 8 months of Google-internal development.	12 years ago
io.h	Sync from internal Google development.	13 years ago

README

This directory contains code that is ANSI C but uses parts of the
standard library that are not available to very limited environments
like Linux Kernel modules.  The standard calls environments like this
"freestanding implementations."

This does *not* imply that the upb core can be compiled directly on a
freestanding implementation.  Even the core uses library functions
that are not directly available on freestanding implementations
(notably malloc()/free(), vsnprintf(), and assert()).  So compiling on
freestanding implementations may require implementing compatibility
versions of functions like malloc().

Also, Linux is not technically a freestanding implementation either,
since it does not accept functions that return float or double on
x86-64 (these use SSE registers which are disabled in kernel mode).