aboutsummaryrefslogtreecommitdiffhomepage
Commit message (Collapse)AuthorAge
* InitializeDefaultRepeatedFields() allocates memory but does not release it.Gravatar Antoni Buszta2014-10-08
|
* Down-integrate from internal branch.Gravatar Feng Xiao2014-10-07
|
* Merge pull request #35 from dsrosario/fix_warningGravatar Feng Xiao2014-10-06
|\ | | | | Fix "warning C4018: '<' : signed/unsigned mismatch"
* \ Merge pull request #38 from xfxyjwf/fix17Gravatar Feng Xiao2014-10-03
|\ \ | | | | | | Fix a bug that causes DynamicMessage.setField() to not work for repeated enum fields.
* | | Down-integrate from internal branch.Gravatar Feng Xiao2014-10-03
| | |
| * | Update verification methods' names.Gravatar Feng Xiao2014-10-02
| | |
* | | Merge pull request #39 from xfxyjwf/fix24Gravatar Feng Xiao2014-10-02
|\ \ \ | | | | | | | | Fix descriptor validation logic for packed enum fields.
* \ \ \ Merge pull request #3 from dhirschfeld/pyext-fixGravatar Feng Xiao2014-10-02
|\ \ \ \ | | | | | | | | | | Explicitly specify pyext/cpp_message.py in py_modules list
| | * | | Fix descriptor validation logic for packed enum fields.Gravatar Feng Xiao2014-10-01
| |/ / / |/| | |
| | * | Fix a bug that causes DynamicMessage.setField() to not work for repeatedGravatar Feng Xiao2014-10-01
| |/ / |/| | | | | | | | enum fields.
* | | Merge pull request #37 from google/fix_linksGravatar xfxyjwf2014-10-01
|\ \ \ | | | | | | | | Replace links to code.google.com/protobuf with developers.google.com/protocol-buffers
| * | | Replace links to code.google.com/protobuf with ↵Gravatar Feng Xiao2014-10-01
|/ / / | | | | | | | | | developers.google.com/protocol-buffers
* | | Merge pull request #32 from worr/bug/solaris-atomicopsGravatar xfxyjwf2014-09-23
|\ \ \ | | | | | | | | Add support for solaris atomicops
| | | * Fix "warning C4018: '<' : signed/unsigned mismatch" at wire_format_lite_inl.hGravatar Dinis Rosário2014-09-23
| |_|/ |/| |
| * | Update CONTRIBUTORS.txtGravatar William Orr2014-09-22
| | |
| * | Update copyright notice and remove first lineGravatar William Orr2014-09-22
| | |
* | | Merge pull request #31 from worr/bug/autoconf-sched-yieldGravatar xfxyjwf2014-09-22
|\ \ \ | | | | | | | | Add check for sched_yield in librt
| | * | Add support for solaris atomicopsGravatar William Orr2014-09-19
| |/ / |/| | | | | | | | | | | | | | This patch adds support for atomic operations on Solaris, on any platform. It makes use of the atomic functions made available in Solaris' atomic.h header.
| * | Add check for sched_yield in librtGravatar William Orr2014-09-19
|/ / | | | | | | | | In Solaris, sched_yield lives in librt, rather than libc. This patch adds a check which will link in librt if necessary.
* | Merge pull request #30 from edmonds/branches/fix_generic_atomicops_memory_modelsGravatar xfxyjwf2014-09-19
|\ \ | | | | | | generic atomicops: promote Acquire_Store() and Release_Load() to use SEQ_CST fence
| * | generic atomicops: promote Acquire_Store() and Release_Load() to use SEQ_CST ↵Gravatar Robert Edmonds2014-09-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | fence __atomic_store_n() cannot take a memory model argument of __ATOMIC_ACQUIRE, and __atomic_load_n() cannot take a memory model argument of __ATOMIC_RELEASE, per the GCC documentation: https://gcc.gnu.org/onlinedocs/gcc-4.9.1/gcc/_005f_005fatomic-Builtins.html On Clang this generates a -Watomic-memory-ordering warning. Promote the fences in Acquire_Store() and Release_Load() to the stronger __ATOMIC_SEQ_CST memory model, which ought to be safe. Note that there are no actual uses of Acquire_Store() or Release_Load() in protobuf, though. This follows the TSAN atomicops implementation, which also uses SEQ_CST fences for these functions. (Fixes #25.)
* | | Merge pull request #29 from ↵Gravatar xfxyjwf2014-09-18
|\ \ \ | |/ / |/| | | | | | | | edmonds/branches/undef_GOOGLE_PROTOBUF_PLATFORM_ERROR platform_macros.h: #undef GOOGLE_PROTOBUF_PLATFORM_ERROR once it's no longer needed
| * | platform_macros.h: #undef GOOGLE_PROTOBUF_PLATFORM_ERROR once it's no longer ↵Gravatar Robert Edmonds2014-09-18
| | | | | | | | | | | | needed
* | | Merge pull request #27 from edmonds/branches/fix_generic_atomicops_non_clangGravatar xfxyjwf2014-09-18
|\| | | | | | | | Fix atomicops build failure on non-Clang
| * | Fix atomicops build failure on non-ClangGravatar Robert Edmonds2014-09-18
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We cannot use Clang's __has_extension macro unless we really are compiling on Clang, which means we cannot use this expression: #if (defined(__clang__) && __has_extension(c_atomic))) // ... #endif On GCC, this generates the following errors: In file included from ./google/protobuf/stubs/atomicops.h:59:0, from google/protobuf/stubs/atomicops_internals_x86_gcc.cc:36: ./google/protobuf/stubs/platform_macros.h:67:41: error: missing binary operator before token "(" (defined(__clang__) && __has_extension(c_atomic))) ^ In file included from google/protobuf/stubs/atomicops_internals_x86_gcc.cc:36:0: ./google/protobuf/stubs/atomicops.h:196:40: error: missing binary operator before token "(" (defined(__clang__) && __has_extension(c_atomic)) ^ Instead, we have to protect the __has_extension expression by only executing it when __clang__ is defined: #if defined(__clang__) # if __has_extension(c_atomic) // ... # endif #endif
* | Merge pull request #21 from edmonds/branches/clang_generic_atomicsGravatar xfxyjwf2014-09-18
|\ \ | | | | | | Expose generic atomicops on Clang
* \ \ Merge pull request #20 from edmonds/branches/no_ppcGravatar xfxyjwf2014-09-18
|\ \ \ | | | | | | | | Remove GOOGLE_PROTOBUF_ARCH_PPC
| | * | Expose generic atomicops on ClangGravatar Robert S. Edmonds2014-09-13
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The generic atomicops implementation is only exposed if GCC >= 4.7 is available, but Clang, where the underlying __atomic built-ins are also available, typically only claims to be GCC 4.2. This causes build failures when compiling protobuf or the output of protoc's C++ code generator on an architecture that needs the generic atomicops implementation with Clang. Clang has a "c_atomic" extension which can be tested for which almost does what we want: C11 atomic operations Use __has_feature(c_atomic) or __has_extension(c_atomic) to determine if support for atomic types using _Atomic is enabled. Clang also provides a set of builtins which can be used to implement the <stdatomic.h> operations on _Atomic types. I'm not sure if this guarantees that the GNU atomic builtins (the ones with the __atomic prefix) are also available, but in practice this should guarantee that Clang is new enough. With this change in place, Clang generates several diagnostics when compiling the generic atomicops implementation. These appear to be bugs in the generic atomicops implementation and are not Clang-specific.
| * / Remove GOOGLE_PROTOBUF_ARCH_PPCGravatar Robert S. Edmonds2014-09-13
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The macro GOOGLE_PROTOBUF_ARCH_PPC is not used anywhere in the protobuf source; there is no Power-specific atomics implementation, etc. Funnily enough, the macro __ppc__ is not actually defined on 32-bit Power on GCC/Linux, according to the following webpage: http://nadeausoftware.com/articles/2012/02/c_c_tip_how_detect_processor_type_using_compiler_predefined_macros#POWER and verified on a 32-bit Debian sid 'powerpc' chroot: (sid_powerpc-dchroot)edmonds@partch:~$ gcc -dM -E - < /dev/null | grep -c __ppc__ 0 (sid_powerpc-dchroot)edmonds@partch:~$ gcc -dM -E - < /dev/null | grep -c __LP64__ 0
* | Merge pull request #15 from google/pom_version_fixGravatar Jisi Liu2014-09-04
|\ \ | | | | | | Bump version for maven-bundle-plugin
| * | Bump version for maven-bundle-pluginGravatar Jisi Liu2014-09-04
|/ /
* | Merge pull request #12 from huahang/patch-2Gravatar Jisi Liu2014-09-03
|\ \ | | | | | | remove a const qualifier in a method's return type
| * | remove a const qualifier in a method's return typeGravatar huahang2014-09-04
|/ /
* | Merge pull request #8 from huahang/patch-1Gravatar Jisi Liu2014-09-03
|\ \ | | | | | | fix a compile warning
| * | fix a compile warningGravatar huahang2014-09-03
|/ / | | | | | | | | This change fixes the following compiler warning: warning: type qualifiers ignored on function return type [-Wignored-qualifiers]
* | Merge pull request #1 from dhirschfeld/vs2008-fixGravatar xfxyjwf2014-09-02
|\ \ | | | | | | Added const qualifier to iterator to enable compiling with VS2008
* | | Rename README.txt to README.mdGravatar Feng Xiao2014-08-29
| | |
* | | Merge pull request #5 from google/fix_readmeGravatar xfxyjwf2014-08-29
|\ \ \ | | | | | | | | Rename README.txt to README.md and use markdown formatting.
| * | | Fix the formating of bold text.Gravatar Feng Xiao2014-08-28
| | | |
| * | | Update README.md to markdown format.Gravatar Feng Xiao2014-08-28
| | | |
| * | | Rename README.txt to README.mdGravatar Feng Xiao2014-08-28
|/ / /
* | | Merge pull request #4 from google/fix_readmeGravatar Jisi Liu2014-08-28
|\ \ \ | | | | | | | | Add instructions on how to generate the configure script.
| * | | Add instructions on how to generate the configure script.Gravatar Feng Xiao2014-08-28
|/ / /
| | * Explicitly specify pyext/cpp_message.py in py_modules listGravatar David Hirschfeld2014-08-27
| |/ |/|
| * Added const qualifier to iterator to enable compiling with VS2008Gravatar David Hirschfeld2014-08-27
|/
* Rename COPYING.txt to LICENSE for opensource compliance and update linksGravatar Feng Xiao2014-08-26
| | | | in README.txt.
* merge 2.6.0 to trunkGravatar jieluo@google.com2014-08-25
|
* merge tags/2.6.0 into trunkGravatar jieluo@google.com2014-08-25
|
* patch Issue 130740043 to trunk for other atomicops patches: [MIPS64] Add ↵Gravatar jieluo@google.com2014-08-20
| | | | support for MIPS64 in protobuf
* make dist complains the file name is too long and refuse to put it to tar. ↵Gravatar jieluo@google.com2014-08-14
| | | | Change the file to a shorter name
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-30 19:20:42 +0000