about summary refs log tree commit diff
path: root/src/test/bench
AgeCommit message (Collapse)AuthorLines
2014-10-24ignore-androidJulian Orth-0/+2
2014-10-24Improve shootout-reverse-complementJulian Orth-88/+259
2014-10-19Remove a large amount of deprecated functionalityAlex Crichton-68/+86
Spring cleaning is here! In the Fall! This commit removes quite a large amount of deprecated functionality from the standard libraries. I tried to ensure that only old deprecated functionality was removed. This is removing lots and lots of deprecated features, so this is a breaking change. Please consult the deprecation messages of the deleted code to see how to migrate code forward if it still needs migration. [breaking-change]
2014-10-17auto merge of #18056 : TeXitoi/rust/shootout-reverse-complement-improvement, ↵bors-12/+46
r=alexcrichton This is some improvement as asked and discused here: http://www.reddit.com/r/rust/comments/2j2ij3/benchmark_improvement_reverse_compliment/ Before: ``` real 0m0.396s user 0m0.280s sys 0m0.112s ``` after: ``` real 0m0.293s user 0m0.216s sys 0m0.076s ``` best C version: ``` real 0m0.135s user 0m0.132s sys 0m0.060s ``` Another possibility will be to add a `DoubleEndedIterator::next_two_side()` with a deffault implementation, and specialising it for slices, and use it here (`MutableSlice::reverse()` can then become safe). This benchmark will then be safe. What do you think?
2014-10-16auto merge of #17989 : alexcrichton/rust/spectralnorm, r=thestingerbors-79/+68
This improves the spectralnorm shootout benchmark through a few vectors after looking at the leading C implementation: * The simd-based f64x2 is now used to parallelize a few computations * RWLock usage has been removed. A custom `parallel` function was added as a form of stack-based fork-join parallelism. I found that the contention on the locks was high as well as hindering other optimizations. This does, however, introduce one `unsafe` block into the benchmarks, which previously had none. In terms of timings, the before and after numbers are: ``` $ time ./shootout-spectralnorm-before ./shootout-spectralnorm-before 2.07s user 0.71s system 324% cpu 0.857 total $ time ./shootout-spectralnorm-before 5500 ./shootout-spectralnorm-before 5500 11.88s user 1.13s system 459% cpu 2.830 total $ time ./shootout-spectralnorm-after ./shootout-spectralnorm-after 0.58s user 0.01s system 280% cpu 0.210 tota $ time ./shootout-spectralnorm-after 5500 ./shootout-spectralnorm-after 5500 3.55s user 0.01s system 455% cpu 0.783 total ```
2014-10-16auto merge of #17947 : lukemetz/rust/master, r=aturonbors-2/+2
AsciiStr::to_lower is now AsciiStr::to_lowercase and AsciiStr::to_upper is AsciiStr::to_uppercase to match Ascii trait. Part of issue #17790. This is my first pull request so let me know if anything is incorrect. Thanks! [breaking-changes]
2014-10-16Remove libdebug and update tests.Luqman Aden-18/+15
2014-10-16shootout-reverse-complement: reimplement TwoSideIter using pointersGuillaume Pinot-23/+32
2014-10-15Renamed AsciiStr::to_lower and AsciiStr::to_upper=-2/+2
Now AsciiStr::to_lowercase and AsciiStr::to_uppercase to match Ascii trait. [breaking-change]
2014-10-14improve shootout-reverse-complement.rs using unsafe codeGuillaume Pinot-11/+36
2014-10-13bench: Improve the spectralnorm shootout benchmarkAlex Crichton-79/+68
This improves the spectralnorm shootout benchmark through a few vectors after looking at the leading C implementation: * The simd-based f64x2 is now used to parallelize a few computations * RWLock usage has been removed. A custom `parallel` function was added as a form of stack-based fork-join parallelism. I found that the contention on the locks was high as well as hindering other optimizations. This does, however, introduce one `unsafe` block into the benchmarks, which previously had none. In terms of timings, the before and after numbers are: ``` $ time ./shootout-spectralnorm-before ./shootout-spectralnorm-before 2.07s user 0.71s system 324% cpu 0.857 total $ time ./shootout-spectralnorm-before 5500 ./shootout-spectralnorm-before 5500 11.88s user 1.13s system 459% cpu 2.830 total $ time ./shootout-spectralnorm-after ./shootout-spectralnorm-after 0.58s user 0.01s system 280% cpu 0.210 tota $ time ./shootout-spectralnorm-after 5500 ./shootout-spectralnorm-after 5500 3.55s user 0.01s system 455% cpu 0.783 total ```
2014-10-11fix shootout-mandelbrot to make it pass the shootout testGuillaume Pinot-1/+9
2014-10-11auto merge of #17936 : TeXitoi/rust/remove-shootout-warnings, r=alexcrichtonbors-31/+33
Only one warning remain, and I can't find a way to remove it without doing more bound checks: ``` shootout-nbody.rs:105:36: 105:51 warning: use of deprecated item: use iter_mut, #[warn(deprecated)] on by default shootout-nbody.rs:105 let bi = match b_slice.mut_shift_ref() { ``` using `split_at_mut` may be an option, but it will do more bound checking. If anyone have an idea, I'll update this PR.
2014-10-11remove shootout warningsGuillaume Pinot-31/+33
2014-10-09test: Convert statics to constantsAlex Crichton-18/+18
Additionally, add lots of tests for new functionality around statics and `static mut`.
2014-10-07Put slicing syntax behind a feature gate.Nick Cameron-1/+13
[breaking-change] If you are using slicing syntax you will need to add #![feature(slicing_syntax)] to your crate.
2014-10-07Use slice syntax instead of slice_to, etc.Nick Cameron-12/+12
2014-10-02Test fixes from the rollupAlex Crichton-2/+2
2014-10-02rollup merge of #17666 : eddyb/take-garbage-outAlex Crichton-19/+9
Conflicts: src/libcollections/lib.rs src/libcore/lib.rs src/librustdoc/lib.rs src/librustrt/lib.rs src/libserialize/lib.rs src/libstd/lib.rs src/test/run-pass/issue-8898.rs
2014-10-02Revert "Use slice syntax instead of slice_to, etc."Aaron Turon-12/+12
This reverts commit 40b9f5ded50ac4ce8c9323921ec556ad611af6b7.
2014-10-02Revert "Put slicing syntax behind a feature gate."Aaron Turon-13/+1
This reverts commit 95cfc35607ccf5f02f02de56a35a9ef50fa23a82.
2014-10-02tests: remove uses of Gc.Eduard Burtescu-19/+9
2014-10-02Put slicing syntax behind a feature gate.Nick Cameron-1/+13
[breaking-change] If you are using slicing syntax you will need to add #![feature(slicing_syntax)] to your crate.
2014-10-02Use slice syntax instead of slice_to, etc.Nick Cameron-12/+12
2014-10-01Remove all use of librustuvAaron Turon-25/+3
2014-09-25Relicense shootout-fasta-redux.rs to the shootout license.Guillaume Pinot-8/+38
Everyone agreed. Fix #17078
2014-09-18auto merge of #17335 : TeXitoi/rust/relicense-shootout, r=brsonbors-22/+77
Everyone agreed. Fix #17064, fix #17072 @brson OK?
2014-09-17rollup merge of #17309 : aturon/deprecate-libnumAlex Crichton-128/+0
2014-09-17Relicense shootout-fasta.rs ti the shootout license.Guillaume Pinot-14/+39
Everyone agreed. Fix #17072
2014-09-17Relicense shootout-spectralnorm.rs to the shootout licenseGuillaume Pinot-8/+38
Everyone agreed. Fix #17064
2014-09-16Fallout from renamingAaron Turon-47/+47
2014-09-16Deprecate libnum in favor of rust-lang/numAaron Turon-128/+0
This is part of the migration of crates into the Cargo ecosystem. There is now an external repository https://github.com/rust-lang/num for bignums. The single use of libnum elsewhere in the repository is for a shootout benchmark, which is being moved into the external crate. Due to deprecation, this is a: [breaking-change]
2014-09-09rollup merge of #17096 : TeXitoi/relicense-shootout-chameneos-reduxAlex Crichton-8/+38
2014-09-09rollup merge of #17077 : TeXitoi/relicense-shootout-nbodyAlex Crichton-8/+38
2014-09-08Relicense shootout-chameneos-redux.rs to the shootout license.Guillaume Pinot-8/+38
Everyone agreed. fix #17076
2014-09-07Relicense shootout-nbody.rs to the shootout licenseGuillaume Pinot-8/+38
Everyone agreed. fix #17073
2014-09-07Relicense shootout-reverse-complement.rs to the shootout license.Guillaume Pinot-8/+38
Everyone agreed. Fix #17065
2014-09-05Optimize Slice::reverseBrian Anderson-195/+1
This makes the completely safe implementation of fannkuchredux perform the same as C++. Yay, Rust.
2014-09-04Update fannkuchredux benchmarkBrian Anderson-48/+325
From the discussion on reddit: http://www.reddit.com/r/rust/comments/2fenlg/benchmark_improvement_fannkuchredux/ This adds two variants: the primary, that uses an unsafe block, and a secondary that is completely safe. The one with the unsafe block matches clang's performance and beats gcc's.
2014-08-30Unify non-snake-case lints and non-uppercase statics lintsP1start-2/+2
This unifies the `non_snake_case_functions` and `uppercase_variables` lints into one lint, `non_snake_case`. It also now checks for non-snake-case modules. This also extends the non-camel-case types lint to check type parameters, and merges the `non_uppercase_pattern_statics` lint into the `non_uppercase_statics` lint. Because the `uppercase_variables` lint is now part of the `non_snake_case` lint, all non-snake-case variables that start with lowercase characters (such as `fooBar`) will now trigger the `non_snake_case` lint. New code should be updated to use the new `non_snake_case` lint instead of the previous `non_snake_case_functions` and `uppercase_variables` lints. All use of the `non_uppercase_pattern_statics` should be replaced with the `non_uppercase_statics` lint. Any code that previously contained non-snake-case module or variable names should be updated to use snake case names or disable the `non_snake_case` lint. Any code with non-camel-case type parameters should be changed to use camel case or disable the `non_camel_case_types` lint. [breaking-change]
2014-08-28auto merge of #16664 : aturon/rust/stabilize-option-result, r=alexcrichtonbors-4/+4
Per API meeting https://github.com/rust-lang/meeting-minutes/blob/master/Meeting-API-review-2014-08-13.md # Changes to `core::option` Most of the module is marked as stable or unstable; most of the unstable items are awaiting resolution of conventions issues. However, a few methods have been deprecated, either due to lack of use or redundancy: * `take_unwrap`, `get_ref` and `get_mut_ref` (redundant, and we prefer for this functionality to go through an explicit .unwrap) * `filtered` and `while` * `mutate` and `mutate_or_set` * `collect`: this functionality is being moved to a new `FromIterator` impl. # Changes to `core::result` Most of the module is marked as stable or unstable; most of the unstable items are awaiting resolution of conventions issues. * `collect`: this functionality is being moved to a new `FromIterator` impl. * `fold_` is deprecated due to lack of use * Several methods found in `core::option` are added here, including `iter`, `as_slice`, and variants. Due to deprecations, this is a: [breaking-change]
2014-08-28Fallout from stabilizing core::optionAaron Turon-4/+4
2014-08-27Implement generalized object and type parameter bounds (Fixes #16462)Niko Matsakis-4/+4
2014-08-26Use temp vars for implicit coercion to ^[T]Nick Cameron-2/+3
2014-08-18regex: Enable test on Windowsklutzy-2/+0
Fixes #13725
2014-08-15auto merge of #16435 : vadimcn/rust/windows, r=pcwaltonbors-1/+1
Using "win32" to mean "Windows" is confusing, especially now, that Rust supports win64 builds. Let's call spade a spade.
2014-08-12Replace "ignore-win32" in tests with "ignore-windows"Vadim Chugunov-1/+1
2014-08-09Fix misspelled comments for tests.Joseph Crail-9/+9
2014-07-26Remove managed_box gate from testsBrian Anderson-2/+1
No longer does anything.
2014-07-26Relicense shootout-k-nucleotide.rsGuillaume Pinot-8/+38
Everyone agreed except @thestinger. As @thestinger contribution on this file is trivial, we can relicense it. Related to #14248, close #15330
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-03-01 22:31:27 +0000