-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/03/11 17:50, Andrew MacLeod wrote: > These are the changes to libstdc++ to make use of the new atomics. > I changed the files to use the new atomics, and bkoz did a > shuffling of the include file layout to better suit the new c++ > approach. > > previously, libstdc++ provided a locked implementation in > atomic_0.h with the theory that eventually it would be used. The > new scheme involves leaving non-lock-free implementations to an > external library. This involved removing the old lock > implementation and restructuring things now that multiple > implementation dont have to be supported. SO a lot fo this is > churn... 2 include files deleted and one merged into another one.. Is there an ABI/API impact to all this churn? Or was the atomic_0.h stuff never used? Was it an exposed API or strictly internal? I get the impression that is_lock_free wasn't ever defined, which is probably good in this context.
Given these are primarily Benjamin's changes, I'm going to defer to his wisdom :-) If he doesn't chime in, ping him directly. jeff -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOtCuOAAoJEBRtltQi2kC7M34H/2B9f1DsPE9oK5DfvHYyclxZ hvFGlSnw5r9q7UGsWrCGDd/J4mmkXOJMHMfpzjowuWUYUYDNZ5b2FuZ9fMij2K5f wJOfN9wslWTNyafJb/hjVMEzy1dmCUB2YV4N0e5cy39lvfWfNzM/9EfYbz5UEQpO VCODtS0WbsSUTkt7HeDkD7U21mpSsn1fGx4gBJyBpODihIq7Qk4uFqGtvrKGve26 7Pi3aP64TQl3zwF2lAkOV4KgzPLQUv4RIWOiYuyzEf13XpfJivWPLTUkJqJka+lp 8W+LFOLl3ygnNUAe9ugwRNCE+agfHG+Hp7+l8ypCpWSsrBwJB8m7rY1sMDA2HJw= =E/Sj -----END PGP SIGNATURE-----
