owner
stringclasses
14 values
repo
stringclasses
14 values
id
int64
116k
4.61B
issue_number
int32
1
181k
author
stringlengths
1
39
body
stringlengths
1
262k
created_at
timestamp[us]date
2000-06-06 02:40:44
2026-06-02 20:16:18
updated_at
timestamp[us]date
2000-06-06 02:40:44
2026-06-02 20:22:56
reactions
unknown
author_association
stringclasses
5 values
swiftlang
swift
4,382,016,640
88,822
coenttb
Live reproducer in production CI on `swift-primitives/swift-tagged-primitives`: https://github.com/swift-primitives/swift-tagged-primitives/actions/runs/25394661323 Same assertion fires on Swift 6.3.1-release (Windows) and Swift 6.4-dev nightly (Linux), both compiling under `-enable-upcoming-feature InternalImportsByD...
2026-05-05T18:39:42
2026-05-05T18:39:42
{}
NONE
swiftlang
swift
4,385,312,808
88,850
xavgru12
Rebase this, make commits for each file and collect them in one PR as xedin suggested
2026-05-06T05:15:24
2026-05-06T05:15:24
{}
CONTRIBUTOR
swiftlang
swift
4,379,703,945
79,176
al45tair
I think we should probably close this, as I don't think it likely that anyone has any plans to do anything with it. If someone wanted to change the meaning of the above import statements, that would need to go through Swift Evolution and there would probably need to be a new language mode as well.
2026-05-05T13:28:32
2026-05-05T13:28:32
{}
CONTRIBUTOR
swiftlang
swift
4,379,889,063
88,733
aidan-hall
@swift-ci test
2026-05-05T13:49:18
2026-05-05T13:49:18
{}
CONTRIBUTOR
swiftlang
swift
4,380,372,326
88,781
egorzhdan
@xtremekforever is correct, this is already fixed in https://github.com/swiftlang/swift/pull/88521 and the fix is scheduled to be shipped in 6.3.2 release.
2026-05-05T14:45:05
2026-05-05T14:45:05
{}
CONTRIBUTOR
swiftlang
swift
4,380,459,670
88,731
mattmassicotte
I agree that if the last release of Xcode 26 ends up contains this bug it will hurt the adoption of `NonisolatedNonsendingByDefault`
2026-05-05T14:55:41
2026-05-05T14:55:41
{ "+1": 2 }
CONTRIBUTOR
swiftlang
swift
4,380,787,252
88,831
Snowy1803
It is when a Swift file is first compiled and output to SIL, then it is compiled as if the source file was this intermediate SIL code. In the debugger, it will step through SIL instructions instead of the original Swift code. According to DebuggingTheCompiler.md, it is used for profiling the standard library.
2026-05-05T15:38:48
2026-05-05T15:38:48
{}
MEMBER
swiftlang
swift
4,384,633,282
88,828
airspeedswift
@swift-ci please smoke test
2026-05-06T02:22:04
2026-05-06T02:22:04
{}
MEMBER
swiftlang
swift
4,384,879,831
88,813
tshortli
@swift-ci please test
2026-05-06T03:37:43
2026-05-06T03:37:43
{}
CONTRIBUTOR
swiftlang
swift
4,379,744,772
75,354
daveinglis
https://github.com/swiftlang/swift-build/pull/1251 @swift-ci test
2026-05-05T13:33:04
2026-05-05T13:33:04
{}
CONTRIBUTOR
swiftlang
swift
4,379,745,734
88,683
egorzhdan
@swift-ci please test
2026-05-05T13:33:09
2026-05-05T13:33:09
{}
CONTRIBUTOR
swiftlang
swift
4,381,325,403
88,759
gottesmm
@swift-ci smoke test
2026-05-05T16:56:01
2026-05-05T16:56:01
{}
CONTRIBUTOR
swiftlang
swift
4,381,945,940
88,787
augusto2112
https://github.com/swiftlang/llvm-project/pull/12890 @swift-ci smoke test
2026-05-05T18:30:29
2026-05-05T18:30:29
{}
CONTRIBUTOR
swiftlang
swift
4,382,352,295
88,829
airspeedswift
@swift-ci please smoke test and merge
2026-05-05T19:29:56
2026-05-05T19:29:56
{}
MEMBER
swiftlang
swift
4,383,095,764
88,726
jckarter
@swift-ci Please test
2026-05-05T21:14:11
2026-05-05T21:14:11
{}
CONTRIBUTOR
swiftlang
swift
4,384,469,353
88,829
airspeedswift
@swift-ci please smoke test windows
2026-05-06T01:38:40
2026-05-06T01:38:40
{}
MEMBER
swiftlang
swift
4,386,047,428
86,666
eeckstein
Generic types/functions are in general much slower than non-generic types/functions. It would be interesting if you see the slowdown even if the generic type gets specialized
2026-05-06T07:47:44
2026-05-06T07:47:44
{}
CONTRIBUTOR
swiftlang
swift
4,380,662,011
88,253
tshortli
@swift-ci please smoke test
2026-05-05T15:21:45
2026-05-05T15:21:45
{}
CONTRIBUTOR
swiftlang
swift
4,380,664,407
88,801
xavgru12
Implemented with #88819. I suspect there could be more uses of this?
2026-05-05T15:22:00
2026-05-05T15:22:00
{}
CONTRIBUTOR
swiftlang
swift
4,380,965,593
88,834
gottesmm
@swift-ci smoke test
2026-05-05T16:04:43
2026-05-05T16:04:43
{}
CONTRIBUTOR
swiftlang
swift
4,382,005,467
88,668
keith
@swift-ci please test
2026-05-05T18:38:10
2026-05-05T18:38:10
{}
MEMBER
swiftlang
swift
4,383,685,353
88,811
xedin
@swift-ci please test
2026-05-05T22:40:34
2026-05-05T22:40:34
{}
CONTRIBUTOR
swiftlang
swift
4,386,064,343
88,825
eeckstein
@swift-ci apple silicon benchmark
2026-05-06T07:50:46
2026-05-06T07:50:46
{}
CONTRIBUTOR
swiftlang
swift
4,379,696,965
88,536
xavgru12
@AnthonyLatsis
2026-05-05T13:27:46
2026-05-05T13:27:46
{}
CONTRIBUTOR
swiftlang
swift
4,380,809,152
88,833
nkcsgexi
@swift-ci please smoke test
2026-05-05T15:41:48
2026-05-05T15:41:48
{}
CONTRIBUTOR
swiftlang
swift
4,380,889,668
88,685
al45tair
Apparently, the problem here is that the `SWIFT_CONTEXT` argument _must_ be the last argument on architectures that do stack-based parameter passing, which in this case includes Wasm. It works where we're doing register-based parameter passing, because it just causes us to use the context register instead of assigning ...
2026-05-05T15:53:19
2026-05-05T15:53:19
{}
CONTRIBUTOR
swiftlang
swift
4,381,050,713
88,801
hectar-glitches
Yes, that was just the first PR
2026-05-05T16:17:13
2026-05-05T16:17:13
{}
CONTRIBUTOR
swiftlang
swift
4,381,096,647
88,685
al45tair
@swift-ci Please smoke test
2026-05-05T16:22:40
2026-05-05T16:22:40
{}
CONTRIBUTOR
swiftlang
swift
4,381,326,726
88,736
gottesmm
@swift-ci smoke test
2026-05-05T16:56:14
2026-05-05T16:56:14
{}
CONTRIBUTOR
swiftlang
swift
4,383,122,443
88,823
hamishknight
@swift-ci please test
2026-05-05T21:17:29
2026-05-05T21:17:29
{}
CONTRIBUTOR
swiftlang
swift
4,383,766,230
88,854
patrykstefanski
@swift-ci please smoke test
2026-05-05T23:00:01
2026-05-05T23:00:01
{}
CONTRIBUTOR
swiftlang
swift
4,384,873,848
88,860
airspeedswift
@swift-ci please smoke test
2026-05-06T03:35:42
2026-05-06T03:35:42
{}
MEMBER
swiftlang
swift
4,385,134,331
88,634
natecook1000
@swift-ci Please smoke test
2026-05-06T04:41:53
2026-05-06T04:41:53
{}
MEMBER
swiftlang
swift
4,386,102,726
88,846
xavgru12
@swift-ci please test macos
2026-05-06T07:58:08
2026-05-06T07:58:08
{}
CONTRIBUTOR
swiftlang
swift
4,380,227,151
88,768
aidan-hall
@swift-ci test windows
2026-05-05T14:26:27
2026-05-05T14:26:27
{}
CONTRIBUTOR
swiftlang
swift
4,381,465,392
88,842
shahmishal
@swift-ci test
2026-05-05T17:16:01
2026-05-05T17:16:01
{}
MEMBER
swiftlang
swift
4,381,533,897
88,843
airspeedswift
@swift-ci please smoke test
2026-05-05T17:26:58
2026-05-05T17:26:58
{}
MEMBER
swiftlang
swift
4,381,642,277
88,839
xedin
This is going to collide with https://github.com/swiftlang/swift/pull/88811
2026-05-05T17:43:20
2026-05-05T17:43:20
{}
CONTRIBUTOR
swiftlang
swift
4,382,001,482
88,248
elsakeirouz
@swift-ci please test
2026-05-05T18:37:37
2026-05-05T18:37:37
{}
CONTRIBUTOR
swiftlang
swift
4,383,707,043
88,697
patrykstefanski
@swift-ci Please Test Source Compatibility
2026-05-05T22:45:48
2026-05-05T22:45:48
{}
CONTRIBUTOR
swiftlang
swift
4,384,204,222
88,859
meg-gupta
@swift-ci test
2026-05-06T00:25:42
2026-05-06T00:25:42
{}
CONTRIBUTOR
swiftlang
swift
4,380,847,350
88,801
xedin
Yes, there are definitely more uses of this left :)
2026-05-05T15:47:03
2026-05-05T15:47:03
{}
CONTRIBUTOR
swiftlang
swift
4,381,023,613
88,831
adrian-prantl
> What is "SIL-based debuginfo"? This is a mode used by compiler developers to get textual SIL-based debug info. It allows you to look at the performance profile of textual SIL instructions rather than source code.
2026-05-05T16:13:12
2026-05-05T16:13:12
{}
CONTRIBUTOR
swiftlang
swift
4,381,267,718
88,836
xavgru12
@swift-ci smoke test
2026-05-05T16:48:17
2026-05-05T16:48:17
{}
CONTRIBUTOR
swiftlang
swift
4,381,566,565
88,501
jamieQ
closing in favor of https://github.com/swiftlang/swift/pull/88730
2026-05-05T17:32:15
2026-05-05T17:32:15
{}
CONTRIBUTOR
swiftlang
swift
4,382,020,767
87,136
coenttb
The minimal repro above also reproduces in real-world CI on `swift-primitives/swift-tagged-primitives`: https://github.com/swift-primitives/swift-tagged-primitives/actions/runs/25394661323 Same assertion at `MoveOnlyAddressCheckerUtils.cpp:1829`, hits identically on Swift 6.3.1-release (Windows) and Swift 6.4-dev nigh...
2026-05-05T18:40:15
2026-05-05T18:40:15
{}
NONE
swiftlang
swift
4,382,382,549
88,668
cachemeifyoucan
> I wonder if always returning `0` is a deliberate design choice. cc: @artemcm @cachemeifyoucan I think this is by design, at least from the beginning. `swift-driver` has a fallback path that invokes `swift-frontend -scan-dependencies`, which kind of expects to always succeed. I think the reason was that dependency ...
2026-05-05T19:34:27
2026-05-05T19:35:16
{}
CONTRIBUTOR
swiftlang
swift
4,386,356,130
86,666
coenttb
Verified — at `-O` the gap closes. The original numbers were a `-Onone` build (the issue's "To Reproduce" runs `swift build`, which defaults to debug): | Toolchain | Mode | Raw | Flat (`_read`) | `Nested.Inline` | |---|---|---:|---:|---:| | 6.2.3 | `-Onone` | 8.9 ns | 16.3 ns | 68.5 ns (7.67×) | | 6.2.3 | `-O` | 1.1 n...
2026-05-06T08:38:56
2026-05-06T08:38:56
{}
NONE
swiftlang
swift
4,380,498,061
88,777
azarovalex
@eeckstein thanks for the review! CI seems green so would appreciate if we can land this PR.
2026-05-05T15:00:34
2026-05-05T15:00:46
{}
CONTRIBUTOR
swiftlang
swift
4,381,364,614
88,811
xedin
@swift-ci please test
2026-05-05T17:02:23
2026-05-05T17:02:23
{}
CONTRIBUTOR
swiftlang
swift
4,381,425,446
88,840
jamieQ
@swift-ci please smoke test
2026-05-05T17:10:13
2026-05-05T17:10:13
{}
CONTRIBUTOR
swiftlang
swift
4,383,834,350
88,664
keith
@swift-ci please test Windows Platform
2026-05-05T23:15:34
2026-05-05T23:15:34
{}
MEMBER
swiftlang
swift
4,381,233,003
88,726
jckarter
@swift-ci Please test
2026-05-05T16:43:34
2026-05-05T16:43:34
{}
CONTRIBUTOR
swiftlang
swift
4,381,502,235
88,730
jamieQ
Note: I think this is generally ready for review, but there are a handful of TODOs that I'd specifically appreciate further feedback on from those more familiar with the code.
2026-05-05T17:21:50
2026-05-05T17:21:50
{}
CONTRIBUTOR
swiftlang
swift
4,381,546,314
88,833
nkcsgexi
@swift-ci please smoke test
2026-05-05T17:29:02
2026-05-05T17:29:02
{}
CONTRIBUTOR
swiftlang
swift
4,382,033,231
88,726
jckarter
@swift-ci Please test
2026-05-05T18:41:53
2026-05-05T18:41:53
{}
CONTRIBUTOR
swiftlang
swift
4,382,740,386
88,813
tshortli
@swift-ci please test macOS
2026-05-05T20:24:20
2026-05-05T20:24:20
{}
CONTRIBUTOR
swiftlang
swift
4,383,080,198
88,849
hectar-glitches
got it
2026-05-05T21:11:27
2026-05-05T21:11:27
{}
CONTRIBUTOR
swiftlang
swift
4,386,063,387
88,825
eeckstein
@swift-ci smoke test
2026-05-06T07:50:36
2026-05-06T07:50:36
{}
CONTRIBUTOR
swiftlang
swift
4,380,909,172
88,801
xavgru12
Will you continue with this task? @hectar-glitches
2026-05-05T15:56:13
2026-05-05T15:56:13
{ "+1": 1 }
CONTRIBUTOR
swiftlang
swift
4,381,294,028
88,771
azarovalex
Closed in favor of https://github.com/swiftlang/swift/pull/88777
2026-05-05T16:51:54
2026-05-05T16:51:54
{}
CONTRIBUTOR
swiftlang
swift
4,382,004,787
88,664
keith
@swift-ci please test
2026-05-05T18:38:05
2026-05-05T18:38:05
{}
MEMBER
swiftlang
swift
4,382,930,967
88,851
airspeedswift
@swift-ci please smoke test
2026-05-05T20:48:58
2026-05-05T20:48:58
{}
MEMBER
swiftlang
swift
4,382,998,735
88,836
xavgru12
@xedin
2026-05-05T20:59:21
2026-05-05T20:59:21
{}
CONTRIBUTOR
swiftlang
swift
4,380,552,694
88,831
Snowy1803
@swift-ci please smoke test
2026-05-05T15:07:55
2026-05-05T15:07:55
{}
MEMBER
swiftlang
swift
4,381,750,276
88,597
patrykstefanski
@swift-ci please smoke test
2026-05-05T17:59:40
2026-05-05T17:59:40
{}
CONTRIBUTOR
swiftlang
swift
4,381,815,362
87,115
allevato
swiftlang/swift-syntax#3268 @swift-ci please smoke test Linux platform
2026-05-05T18:10:08
2026-05-05T18:10:08
{}
MEMBER
swiftlang
swift
4,382,946,050
88,849
xedin
@hectar-glitches for the rest of them, let's combine it all in one PR.
2026-05-05T20:50:33
2026-05-05T20:50:33
{ "+1": 1 }
CONTRIBUTOR
swiftlang
swift
4,383,336,658
88,832
egorzhdan
@swift-ci please smoke test macOS
2026-05-05T21:38:03
2026-05-05T21:38:03
{}
CONTRIBUTOR
swiftlang
swift
4,384,122,615
88,858
meg-gupta
@swift-ci test
2026-05-06T00:08:19
2026-05-06T00:08:19
{}
CONTRIBUTOR
swiftlang
swift
4,385,307,068
88,848
xavgru12
Superseded by #88849
2026-05-06T05:13:52
2026-05-06T05:13:52
{}
CONTRIBUTOR
swiftlang
swift
4,381,654,216
88,832
egorzhdan
@swift-ci please smoke test
2026-05-05T17:44:59
2026-05-05T17:44:59
{}
CONTRIBUTOR
swiftlang
swift
4,381,661,262
88,273
aidan-hall
@swift-ci smoke test macos
2026-05-05T17:45:57
2026-05-05T17:45:57
{}
CONTRIBUTOR
swiftlang
swift
4,383,952,469
88,847
meg-gupta
@swift-ci test
2026-05-05T23:32:31
2026-05-05T23:32:31
{}
CONTRIBUTOR
swiftlang
swift
4,385,114,091
88,861
airspeedswift
@swift-ci please smoke test
2026-05-06T04:36:57
2026-05-06T04:36:57
{}
MEMBER
swiftlang
swift
4,297,893,649
88,175
broken-circle
Opened #88827.
2026-04-22T16:08:13
2026-05-06T23:01:17
{}
CONTRIBUTOR
swiftlang
swift
4,392,990,259
88,783
meg-gupta
@jamieQ Thanks for your comments. I am not planning to merge this as-is. InstructionIndices can overflow when blocks and we'll need to keep the slow path around in that case. https://github.com/swiftlang/swift/pull/88774 regained all the benefits this change introduced anyway for a specific test for now.
2026-05-06T23:39:31
2026-05-06T23:44:13
{ "+1": 1 }
CONTRIBUTOR
swiftlang
swift
4,394,571,505
88,794
eeckstein
I could not reproduce the problem
2026-05-07T06:18:15
2026-05-07T06:18:15
{}
CONTRIBUTOR
swiftlang
swift
4,396,483,893
88,872
kathygray-pl
Yeah for test improvement
2026-05-07T10:55:51
2026-05-07T10:55:51
{}
CONTRIBUTOR
swiftlang
swift
4,396,699,644
88,641
kathygray-pl
My other PR #88776 is also relevant
2026-05-07T11:28:41
2026-05-07T11:28:41
{}
CONTRIBUTOR
swiftlang
swift
4,396,956,975
87,115
allevato
I think I see what looks like a non-flaky test failure digging through the logs, in swiftpm I think: ``` [2026-05-06T22:00:07.326Z] ◇ Test case passing 2 arguments buildSystem → .native, testData → MigrateCommandTestData(featureName: "ExistentialAny", expectedSummary: "Applied 5 fix-its in 1 file") to migrateComman...
2026-05-07T12:08:20
2026-05-07T12:08:20
{}
MEMBER
swiftlang
swift
4,397,000,949
88,886
tshortli
https://github.com/swiftlang/llvm-project/pull/12912 @swift-ci please test macOS
2026-05-07T12:14:55
2026-05-07T12:14:55
{}
CONTRIBUTOR
swiftlang
swift
4,392,871,788
88,897
duow310
> Let's use ${Python3_EXECUTABLE} Pushed an update to do that
2026-05-06T23:09:39
2026-05-06T23:09:47
{}
CONTRIBUTOR
swiftlang
swift
4,392,901,808
88,899
nkcsgexi
@swift-ci please smoke test
2026-05-06T23:17:02
2026-05-06T23:17:02
{}
CONTRIBUTOR
swiftlang
swift
4,396,458,539
88,872
hamishknight
@swift-ci please smoke test
2026-05-07T10:51:52
2026-05-07T10:51:52
{}
CONTRIBUTOR
swiftlang
swift
4,398,229,133
57,904
marcomasser
FYI: This issue is still there in Swift 6.3.2.
2026-05-07T14:55:27
2026-05-07T14:55:27
{}
NONE
swiftlang
swift
4,398,303,847
88,918
kovdan01
@swift-ci Please test macOS platform
2026-05-07T15:04:40
2026-05-07T15:04:40
{}
CONTRIBUTOR
swiftlang
swift
4,398,307,948
88,920
kovdan01
Tagging @asl @JaapWijnen
2026-05-07T15:05:09
2026-05-07T15:05:09
{}
CONTRIBUTOR
swiftlang
swift
4,392,827,575
88,775
compnerd
@swift-ci please test Windows platform
2026-05-06T23:00:07
2026-05-06T23:00:07
{}
MEMBER
swiftlang
swift
4,394,190,801
88,864
hnrklssn
Reproduced in a recent snapshot. Stack trace indicates it crashes in `swift::irgen::IRGenerator::emitLazyDefinitions()`, which is quite late in the pipeline... I'll debug a bit more and see what I can find.
2026-05-07T04:36:41
2026-05-07T04:36:41
{ "+1": 1 }
MEMBER
swiftlang
swift
4,394,221,400
88,825
eeckstein
@swift-ci smoke test
2026-05-07T04:46:12
2026-05-07T04:46:12
{}
CONTRIBUTOR
swiftlang
swift
4,392,819,675
88,851
airspeedswift
@swift-ci please smoke test macOS platform
2026-05-06T22:58:35
2026-05-06T22:58:35
{}
MEMBER
swiftlang
swift
4,392,856,760
88,880
rauhul
I'm not seeing the behavior you describe: ```sh $ swiftc -I . foo.swift foo.swift:4:21: error: cannot convert value of type 'UnsafeBufferPointer<Element>' to expected argument type 'UnsafePointer<Element>' 2 | 3 | func foo(_ inputs: UnsafeBufferPointer<Element>, _ outputs: UnsafeMutableBufferPointer<Element>) { 4 | ...
2026-05-06T23:06:00
2026-05-06T23:06:00
{}
MEMBER
swiftlang
swift
4,393,420,927
88,742
hnrklssn
Thank you for the bug report, @ephemer! Are you able to install a main snapshot (https://www.swift.org/install/macos/) and reproduce it using the latest version also? CC @egorzhdan
2026-05-07T01:31:11
2026-05-07T01:31:11
{}
MEMBER
swiftlang
swift
4,394,397,005
88,880
rauhul
@hnrklssn ah yes `-enable-experimental-feature SafeInteropWrappers` does make the imported api from swiftc use buffer pointers, though I'm not really sure thats the ideal behavior. It seems like you _might_ want an `Unsafe[Mutable]Pointer<InlineArray<N, T>>`
2026-05-07T05:39:38
2026-05-07T05:39:38
{}
MEMBER
swiftlang
swift
4,394,589,575
88,904
hnrklssn
Just because I'm curious: is there a reason for diagnosing this in IRGen rather than the frontend?
2026-05-07T06:20:53
2026-05-07T06:20:53
{}
MEMBER
swiftlang
swift
4,397,004,182
88,894
tshortli
https://github.com/swiftlang/llvm-project/pull/12912 @swift-ci please smoke test macOS
2026-05-07T12:15:24
2026-05-07T12:15:24
{}
CONTRIBUTOR
swiftlang
swift
4,397,009,186
88,894
tshortli
https://github.com/swiftlang/llvm-project/pull/12912 @swift-ci please smoke test Linux
2026-05-07T12:16:07
2026-05-07T12:16:07
{}
CONTRIBUTOR
swiftlang
swift
4,392,986,187
88,900
lorentey
@swift-ci test
2026-05-06T23:38:22
2026-05-06T23:38:22
{}
MEMBER
swiftlang
swift
4,393,070,852
88,342
Catfish-Man
@swift-ci please test
2026-05-07T00:01:01
2026-05-07T00:01:01
{}
CONTRIBUTOR