Commit Graph

10 Commits

Author SHA1 Message Date
Allan Shortlidge
cb578172ea Tests: Remove -disable-availability-checking in more tests that use concurrency.
Use the `%target-swift-5.1-abi-triple` substitution to compile the tests for
deployment to the minimum OS versions required for use of _Concurrency APIs,
instead of disabling availability checking.
2024-10-19 12:35:20 -07:00
Finagolfin
325147f3ec [armv7] Fix static-vtable-stubs test for 32-bit platforms 2024-01-16 15:56:08 +05:30
Steven Wu
52f0d00388 [Test] XFAIL IRGen/static-vtable-stubs.swift on arm64_32
Follow up on https://github.com/apple/swift/pull/70551, also XFAIL the
test on arm64_32.
2023-12-20 09:25:55 -08:00
Steven Wu
496c05d263 [Test] XFAIL IRGen/static-vtable-stubs.swift on armv7k
XFAIL IRGen/static-vtable-stubs.swift on armv7k after fixing it to
correctly using %target-swift-frontend.
2023-12-19 17:26:15 -08:00
Steven Wu
407674ea52 [Test] Fix the wrong subsitution of swift-frontend-target in tests
There is no `%swift-frontend-target` subsitution in test, which is
actually `%target-swift-frontend`. The wrong spelling is actually
interpreted by lit as `%swift`-frontend-target, and surprising didn't
break any tests as the last argument from subsitution is
`-define-availability` so it just leads to an very akward availability
definition.
2023-12-18 16:07:48 -08:00
Arnold Schwaighofer
a4b82e5c20 [rebranch] Fix dead method tests
The internal method _swift_dead_method_stub is renamed by llvm optimizations to one of its aliases.

rdar://113414374
2023-08-09 07:47:49 -07:00
Arnold Schwaighofer
3b5ebaa46c Fix some tests in IRGen folder 2023-06-21 10:10:32 -07:00
Arnold Schwaighofer
c1a93e0bde Move tests over to use the %use_no_opaque_pointers option 2023-06-14 10:49:48 -07:00
Erik Eckstein
82b24ba165 IRGen: fix async vtable stubs
For deleted async vtable methods we need to create a async function pointer.

Fixes a missing-symbol linker error
rdar://108924001
2023-05-16 11:49:11 +02:00
Saleem Abdulrasool
e5cc525136 IRGen: loosen linkage on vtable stubs for static linking
The linkage inferred by internal linking is overly restrictive.  It uses
the "internal linkage type" which is for translation unit local symbols,
that is `static` storage.  These symbols participate in linking and need
to be given external storage but hidden visibility and no DLL storage in
static linking.  This permits them to participate in symbolic resolution
during linking but are made module local, not LLVM module local.
2022-03-01 08:09:37 -08:00