aboutsummaryrefslogtreecommitdiffstats
path: root/components/style/thread_state.rs
Commit message (Collapse)AuthorAgeFilesLines
* Move Stylo to its own repo (#31350)Delan Azabani2024-02-271-97/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | * Remove packages that were moved to external repo * Add workspace dependencies pointing to 2023-06-14 branch * Fix servo-tidy.toml errors * Update commit to include #31346 * Update commit to include servo/stylo#2 * Move css-properties.json lookup to target/doc/stylo * Remove dependency on vendored mako in favour of pypi dependency This also removes etc/ci/generate_workflow.py, which has been unused since at least 9e71bd6a7010d6e5723831696ae0ebe26b47682f. * Add temporary code to debug Windows test failures * Fix failures on Windows due to custom target dir * Update commit to include servo/stylo#3 * Fix license in tests/unit/style/build.rs * Document how to build with local Stylo in Cargo.toml
* Update MPL license to https (part 4)Jan Andre Ikenmeyer2018-11-191-1/+1
|
* Bump bitflags to 1.0 in every servo crateBastien Orivel2017-10-301-10/+10
|
* Backed out changeset e64e659c077d: servo PR #18809 and revendor for reftest ↵Gecko Backout2017-10-191-10/+10
| | | | | | failures, e.g. in layout/reftests/bugs/392435-1.html. r=backout on a CLOSED TREE Backs out https://github.com/servo/servo/pull/18809
* Update bitflags to 1.0 in every servo crateBastien Orivel2017-10-191-10/+10
| | | | | It still needs dependencies update to remove all the other bitflags versions.
* style: allow re-initializing thread_state as long as it's with the same value.Emilio Cobos Álvarez2017-10-081-1/+3
| | | | This unbusts running multiple rule-tree benchmarks at the same time.
* Explicitly register rayon threads, rather than assuming that as the default.Bobby Holley2017-09-191-8/+6
| | | | MozReview-Commit-ID: E4kUyy8HjmV
* Eliminate the now-unnecessary internal mod in thread_state.Bobby Holley2017-09-191-45/+40
| | | | MozReview-Commit-ID: 2d7lvQx7jOf
* Make the thread_state machinery behave the same across debug and opt builds.Bobby Holley2017-09-191-26/+5
| | | | | | | | I don't need this per se, but it seems like a footgun for the methods to return incorrect information depending on the build type. I don't see anywhere where the overhead would be at all significant. MozReview-Commit-ID: G1qyUFhI0aB
* Tidy up rust code with regard to new rule (no = in beginning of line)Jure Podgoršek2017-01-061-2/+2
|
* style: Cleanup and document thread_state.rsEmilio Cobos Álvarez2016-12-311-3/+17
|
* style: Simplify initialization of thread_state.Emilio Cobos Álvarez2016-12-251-4/+3
|
* style: Use rayon instead of our custom work queue.Emilio Cobos Álvarez2016-11-141-1/+2
|
* Concurrent rule tree, v1Emilio Cobos Álvarez2016-11-051-0/+4
| | | | | | | | | | | | This patch introduces infrastructure for the rule tree, and constructs it. We don't use it yet, nor have good heuristics for GC'ing it, but this should not happen anymore once we store the rule node reference in the node. I haven't messed up with memory orders because I want to do a try run with it, then mess with them. Take down the ApplicableDeclarationsCache, use the rule tree for doing the cascade.
* Move thread_state to style.Ms2ger2016-08-221-0/+105
generated by cgit v1.2.3 (git 2.25.1) at 2025-04-29 14:26:49 +0000