The test is loosely based off LLD-ELF's thinlto.ll. However, I
found that test questionable because the the -save_temps behavior it
checks for is identical regardless of whether we are running in single-
or multi-threaded mode. I tried writing a test based on --time-trace
but couldn't get it to run deterministically... so I've opted to just
skip checking that behavior for now.
Details
Details
- Reviewers
gkm - Group Reviewers
Restricted Project - Commits
- rG050a7a27ca84: [lld-macho] Support --thinlto-jobs
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Unit Tests
Unit Tests
Time | Test | |
---|---|---|
280 ms | x64 debian > lld.MachO::thinlto-jobs.ll |
Event Timeline
lld/test/MachO/Inputs/time_trace_tid_count.py | ||
---|---|---|
17 | print(len(set(event['tid'] for event in events if event['name'] == event_name))) |
Comment Actions
Welp, seems like this test is nondeterministic, even though it passes reliably on my local machine. Any ideas? Otherwise I guess we can just land this without tests