On Thu, Dec 6, 2012 at 9:53 AM, Jakub Jelinek <ja...@redhat.com> wrote:
> On i?86/x86_64 it is provided for all targets, but only some of the targets > build libsanitizer then. Either users get errors at compile time (missing > compiler support), or at link time (missing library support). > I think the compiler side should error out if the compiler can't support it > for some reason, if the only reason is missing library support, you should > get a link error. This is my concern. If the library support is not present, I think it is a worse user experience to fail with a link error because that does not communicate to the user if the feature is supported or not. The library could be missing because it was not installed correctly or some user error. And I think that it annoys the user to progress most of the way through the build and fail later. If the compiler can know that the feature is not supported, it should inform the user early and with a message directly from the compiler. The details of the reason for lack of support are of interest to the GCC developer, not the end user. Thanks, David
