misc cleanups

Author: fee1-dead

crates/rustc_codegen_spirv/src/builder/intrinsics.rs

@@ -122,7 +122,7 @@ impl<'a, 'tcx> IntrinsicCallMethods<'tcx> for Builder<'a, 'tcx> {
 
             sym::saturating_add => {
                 assert_eq!(arg_tys[0], arg_tys[1]);
-                let result = match &arg_tys[0].kind() {
+                let result = match arg_tys[0].kind() {
                     TyKind::Int(_) | TyKind::Uint(_) => {
                         self.add(args[0].immediate(), args[1].immediate())
                     }

crates/rustc_codegen_spirv/src/codegen_cx/constant.rs

@@ -437,7 +437,7 @@ impl<'tcx> CodegenCx<'tcx> {
         // println!(
         //     "Creating const alloc of type {} with {} bytes",
         //     self.debug_type(ty),
-        //     alloc.len()
+        //     alloc.inner().len()
         // );
         let mut offset = Size::ZERO;
         let result = self.read_from_const_alloc(alloc, &mut offset, ty);

tests/README.md

@@ -9,9 +9,9 @@ whether it should succeed compilation, or fail. If it is expected to fail, there
 The `src` folder here is the tool that iterates over every file in the `ui` folder. It uses the
 `compiletests` library, taken from rustc's own compiletest framework.
 
-You can run compiletests via `cargo compiletests`. This is an alias set up in `.cargo/config` for
+You can run compiletests via `cargo compiletest`. This is an alias set up in `.cargo/config` for
 `cargo run --release -p compiletests --`. You can filter to run specific tests by passing the
-(partial) filenames to `cargo compiletests some_file_name`, and update the `.stderr` files to
+(partial) filenames to `cargo compiletest some_file_name`, and update the `.stderr` files to
 contain new output via the `--bless` flag (with `--bless`, make sure you're actually supposed to be
 changing the .stderr files due to an intentional change, and hand-validate the output is correct
 afterwards).