| Commit message (Collapse) | Author | Age |
... | |
| | | |
| | | |
| | | |
| | | | |
mac version to that if atomic is enabled
|
|/ / / |
|
| | |
| | |
| | |
| | |
| | |
| | | |
The size parameter is only used in cases where the compiler supports
sized delete, so when that's not available we need to specifically cast
it to void to prevent a warning.
|
|\ \ \
| | | |
| | | | |
[arm/gcc] Don't rely on KUSER_HELPERS feature for atomics
|
|\ \ \ \
| | | | |
| | | | | |
generic atomicops: Use strong compare_exchange
|
| | | | |
| | | | |
| | | | | |
When running >bazel test :protobuf_test a few compiler warnings came up. They were centered around the usage of "int" as the loop counter where the value should have been a size_t.
|
|/ / / /
| | | |
| | | |
| | | |
| | | | |
Weak compare-and-exchange are allowed to fail spuriously, so we have
to use the strong variation here.
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
ARM specific CONFIG_KUSER_HELPERS feature can be disabled in Linux kernel,
and in this case, we shouldn't crash. Use gcc built-in functions instead
of arm specific code if they are available.
|
| |/
|/| |
|
| | |
|
| | |
|
|\ \
| |/
|/| |
|
| |\
| | |
| | | |
Fix MSVC build when HAVE_LONG_LONG is defined.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There seem to already be .proto files out there that have conflicting
enum names, which will not be able to build successfully for some
languages (like C#). To prevent this problem from spreading, let's make
it an error for proto3 but just issue a warning for proto2. This fixes
issue #2179.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
A bug was causing generated JSPB code with CommonJS-style imports to
refer incorrectly to nested messages from other .proto files. The
generated code would have things like "test_pb.InnerMessage" instead of
"test_pb.OuterMessage.InnerMessage". This commit fixes the problem by
correctly taking into account any message nesting.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Change-Id: I6a5078b6bcdf4637e11c1cb9da1f74298e6fc26e
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
(#2146)
Currently deserialization of a non-packed binary repeated field is quadratic in
the number of elements, because each time we parse a new element we copy over
all elements we have parsed so far. This CL fixes the performance problem by
having the generated deserialization code just call addX() instead of using
getX() and setX().
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| | | |
| | | | |
Fixed references to foreign nested messages with CommonJS-style imports
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
There seem to already be .proto files out there that have conflicting
enum names, which will not be able to build successfully for some
languages (like C#). To prevent this problem from spreading, let's make
it an error for proto3 but just issue a warning for proto2. This fixes
issue #2179.
|
| | |/
| |/| |
|
| |/
| |
| |
| |
| |
| |
| |
| | |
A bug was causing generated JSPB code with CommonJS-style imports to
refer incorrectly to nested messages from other .proto files. The
generated code would have things like "test_pb.InnerMessage" instead of
"test_pb.OuterMessage.InnerMessage". This commit fixes the problem by
correctly taking into account any message nesting.
|
|\ \
| | |
| | | |
Merge 3.0.x into master.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Change-Id: I6a5078b6bcdf4637e11c1cb9da1f74298e6fc26e
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
(#2146)
Currently deserialization of a non-packed binary repeated field is quadratic in
the number of elements, because each time we parse a new element we copy over
all elements we have parsed so far. This CL fixes the performance problem by
having the generated deserialization code just call addX() instead of using
getX() and setX().
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/
|/| |
|
|\ \
| | |
| | | |
Merge 3.0.x into master
|
|\ \ \
| | | |
| | | | |
Update the ObjC version checks to support a min and current version.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- Capture the version used to generated.
- Check at compile time and runtime that generated code isn't from a newer
version, also check that the min version required is also supported.
- Keep the old constants/macros/functions to special case the last version
that was working so those generated sources still work until we decide
otherwise.
|
|/ / /
| | |
| | |
| | |
| | | |
This pull request includes two implementation: C extension and PHP
package. Both implementations support encode/decode of singular,
repeated and map fields.
|