Skip to content

Commit 505f9ba

Browse files
authored
Merge pull request #26238 from gottesmm/pr-47e6f8c3558bd10b31ebeb6878aa5da02495f0be
2 parents 55badd6 + c6c8133 commit 505f9ba

File tree

1 file changed

+9
-16
lines changed

1 file changed

+9
-16
lines changed

benchmark/README.md

Lines changed: 9 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,8 @@
1-
Swift Benchmark Suite
2-
=====================
1+
# Swift Benchmark Suite
32

43
This directory contains the Swift Benchmark Suite.
54

6-
Running Swift Benchmarks
7-
------------------------
5+
## Running Swift Benchmarks
86

97
To run Swift benchmarks, pass the `--benchmark` flag to `build-script`. The
108
current benchmark results will be compared to the previous run's results if
@@ -16,8 +14,7 @@ impacting changes, and run the benchmarks again. Upon benchmark completion, the
1614
benchmark results for the development branch will be compared to the most
1715
recent benchmark results for `master`.
1816

19-
Building with build-script
20-
--------------------------
17+
## Building with build-script
2118

2219
By default, Swift benchmarks for OS X are compiled during the Swift build
2320
process. To build Swift benchmarks for additional platforms, pass the following
@@ -33,8 +30,7 @@ drivers dynamically link Swift standard library dylibs from a path
3330
relative to their run-time location (../lib/swift) so the standard
3431
library should be distributed alongside them.
3532

36-
Building Independently
37-
----------------------
33+
## Building Independently
3834

3935
To build the Swift benchmarks using only an Xcode installation: install an
4036
Xcode version with Swift support, install cmake 2.8.12, and ensure Xcode is
@@ -110,8 +106,7 @@ installed libraries instead, enable
110106
This will reflect the performance of the Swift standard library
111107
installed on the device, not the one included in the Swift root.
112108

113-
Using the Benchmark Driver
114-
--------------------------
109+
## Using the Benchmark Driver
115110

116111
### Usage
117112

@@ -154,17 +149,15 @@ You can use test numbers instead of test names like this:
154149
Test numbers are not stable in the long run, adding and removing tests from the
155150
benchmark suite will reorder them, but they are stable for a given build.
156151

157-
Using the Harness Generator
158-
---------------------------
152+
## Using the Harness Generator
159153

160154
`scripts/generate_harness/generate_harness.py` runs `gyb` to automate generation
161155
of some benchmarks.
162156

163157
** FIXME ** `gyb` should be invoked automatically during the
164158
build so that manually invoking `generate_harness.py` is not required.
165159

166-
Adding New Benchmarks
167-
---------------------
160+
## Adding New Benchmarks
168161

169162
The harness generator supports both single and multiple file tests.
170163

@@ -244,8 +237,8 @@ public func run_YourTestName(N: Int) {
244237
The current set of tags are defined by the `BenchmarkCategory` enum in
245238
`TestsUtils.swift` .
246239

247-
Testing the Benchmark Drivers
248-
-----------------------------
240+
## Testing the Benchmark Drivers
241+
249242
When working on tests, after the initial build
250243
````
251244
swift-source$ ./swift/utils/build-script -R -B

0 commit comments

Comments
 (0)