Lines Matching refs:changes

104 consistently helps land code changes that stick, and help reduce the likelihood
113 changes to xnu such that it builds without any diagnostics, and testing at desk
114 that your changes did not impact kernel functionality.
118 debugged bounds checks. You should also use bound-checks-debug for xnu changes
123 Once you're confident in your code changes, everything builds, at-desk testing
126 * one pull request with the necessary adoption code changes, configuring the
128 * one pull request that changes `bound-checks-pending` to `bound-checks-soft`.
130 This strategy can save your change and other people's changes even in the face
171 change. Reverting entire changes is a very destructive integration action: any
172 _other_ changes that rely on your modifications may need to be cascaded out of
176 non-trivial code changes with the enablement of -fbounds-safety is a recipe for
191 We let changes with `bound-checks-soft` steep in internal releases to build up