I agree that it is much nicer to be able to use feature tests/macros instead of compiler-version ifdefs. But library headers really don't have any other way to work around compiler bugs or use new compiler features. One can not expect from library users that they will correctly define all required feature macros.
Regarding the development of distri compiler specifc code: I don't believe the macro would get much use other than the __GNUC_PATCHLEVEL__ macro gets. Are you afraid of developers trying to cripple a distri they don't like? Can you come up with a scenario where a developer would make use of a distri specific define resulting in breakage on other distris? I find this very hard to imagine. (Yes, there are developers that do lots of stupid things, but the only thing to keep them from breaking stuff is to have them stop programming. ;-) ) I understood you don't want to change the gcc 4.5.2 package at all? I'd be happy for any, whatsoever small update to Natty gcc-4.5 that makes it possible to work around the bug. So if you were to add the _MM_MASKSTORE_PS_NEEDS_NATTY_WORKAROUND define that would be a welcome help. I don't care much for how bad the ifdefs become. I can put that logic in an extra code section which defines my feature macros... But I'd hate for these things to only be fixable after a lengthy discussion on a bugtracker, which is why I'd really like to have a macro do determine the differences from the vanilla GCC release. These kind of incompatibilities happened before and will happen again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/780551 Title: incorrect interface in avxintrin.h -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
