forked from OSchip/llvm-project
[libc++] Fix too stringent availability markup for bad_optional_access
The availability markup for bad_optional_access marked it as being added in MacOS 10.14 and aligned releases, however it appears to have been added in Mac OS 10.13 and aligned releases.
This commit is contained in:
parent
e7c5412b37
commit
7fb40e1569
|
@ -1392,10 +1392,10 @@ _LIBCPP_FUNC_VIS extern "C" void __sanitizer_annotate_contiguous_container(
|
|||
__attribute__((availability(tvos,strict,introduced=10.0))) \
|
||||
__attribute__((availability(watchos,strict,introduced=3.0)))
|
||||
# define _LIBCPP_AVAILABILITY_BAD_OPTIONAL_ACCESS \
|
||||
__attribute__((availability(macosx,strict,introduced=10.14))) \
|
||||
__attribute__((availability(ios,strict,introduced=12.0))) \
|
||||
__attribute__((availability(tvos,strict,introduced=12.0))) \
|
||||
__attribute__((availability(watchos,strict,introduced=5.0)))
|
||||
__attribute__((availability(macosx,strict,introduced=10.13))) \
|
||||
__attribute__((availability(ios,strict,introduced=11.0))) \
|
||||
__attribute__((availability(tvos,strict,introduced=11.0))) \
|
||||
__attribute__((availability(watchos,strict,introduced=4.0)))
|
||||
# define _LIBCPP_AVAILABILITY_BAD_VARIANT_ACCESS \
|
||||
_LIBCPP_AVAILABILITY_BAD_OPTIONAL_ACCESS
|
||||
# define _LIBCPP_AVAILABILITY_BAD_ANY_CAST \
|
||||
|
|
|
@ -857,8 +857,8 @@ class Configuration(object):
|
|||
self.config.available_features.add('dylib-has-no-shared_mutex')
|
||||
self.lit_config.note("shared_mutex is not supported by the deployment target")
|
||||
# Throwing bad_optional_access, bad_variant_access and bad_any_cast is
|
||||
# supported starting in macosx10.14.
|
||||
if name == 'macosx' and version in ('10.%s' % v for v in range(9, 14)):
|
||||
# supported starting in macosx10.13.
|
||||
if name == 'macosx' and version in ('10.%s' % v for v in range(9, 13)):
|
||||
self.config.available_features.add('dylib-has-no-bad_optional_access')
|
||||
self.lit_config.note("throwing bad_optional_access is not supported by the deployment target")
|
||||
|
||||
|
|
Loading…
Reference in New Issue