[
https://issues.apache.org/jira/browse/AVRO-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Douglas Creager resolved AVRO-1038.
-----------------------------------
Resolution: Fixed
I agree on both counts. I've checked in the simple fix for 1.6.3, since we can
fall back on the assembly implementation. And I agree that I'd prefer a
preprocessor-based solution, if we can find one for this combination of
versions and platforms.
> Avro-C: Header file calls out GCC atomic intrinsics, which are missing in
> some GCC versions older than 4.5.0
> ------------------------------------------------------------------------------------------------------------
>
> Key: AVRO-1038
> URL: https://issues.apache.org/jira/browse/AVRO-1038
> Project: Avro
> Issue Type: Bug
> Components: c
> Affects Versions: 1.6.2
> Environment: Linux on an x86 or x86-64 platform with GCC versions
> between 4.1.0 and 4.5.0.
> Two platforms we tested were:
> 1. GCC 4.1.2 20080704 (Red Hat 4.1.2-48)
> 2. GCC 4.4.3 on Mandriva for an i586 target
> Reporter: Vivek Nadkarni
> Fix For: 1.6.3
>
> Attachments: AVRO-1038.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> This issue was described as Item 2 in AVRO-1033. Splitting it out into a
> separate JIRA ticket per Doug's request.
> While compiling Avro across several flavors of
> Linux, we noticed that the GCC atomic intrinsics
> __sync_add_and_fetch() and __sync_sub_and_fetch() were not implemented
> for all versions of GCC greater than 4.1.0, causing compile errors.
> Specifically, the following two versions of GCC don't appear to
> support the GCC atomic intrinsics:
> 1. GCC 4.1.2 20080704 (Red Hat 4.1.2-48)
> 2. GCC 4.4.3 on Mandriva for an i586 target
> In our local code we have updated the GCC version test in refcount.h
> to require versions of GCC greater than 4.5.0, before including the
> GCC intrinsics. We might want to do the same in the global Avro
> repository.
> Cheers,
> Vivek Nadkarni
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
