docs: apply some redirects

Here's a few redirects that we should apply, in case the redirects
gets removed in the future.

These are mostly of the 301 (moved permanently) kind, but also a
few where the site probably *should* have used the permanent
error-code.

Reviewed-by: Eric Engestrom <eric@igalia.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19574>

docs/drivers/d3d12.rst

@@ -45,8 +45,8 @@ environment variables:
 ``dump_module``
    dump module tree to stderr
 
-.. _debug layer: https://docs.microsoft.com/en-us/windows/win32/direct3d12/understanding-the-d3d12-debug-layer
-.. _GPU validator: https://docs.microsoft.com/en-us/windows/win32/direct3d12/using-d3d12-debug-layer-gpu-based-validation
+.. _debug layer: https://learn.microsoft.com/en-us/windows/win32/direct3d12/understanding-the-d3d12-debug-layer
+.. _GPU validator: https://learn.microsoft.com/en-us/windows/win32/direct3d12/using-d3d12-debug-layer-gpu-based-validation
 
 Utilities
 ---------

docs/drivers/lima.rst

@@ -252,6 +252,6 @@ Reference
 ---------
 
 Luc Verhaegen’s original Lima site:
-https://web.archive.org/web/20180106112822/http://limadriver.org/
+https://web.archive.org/web/20180101212947/http://limadriver.org/
 
-.. _Mesa issue: https://gitlab.freedesktop.org/mesa/mesa/issues?label_name%5B%5D=lima
+.. _Mesa issue: https://gitlab.freedesktop.org/mesa/mesa/-/issues?label_name%5B%5D=lima

docs/drivers/llvmpipe.rst

@@ -255,14 +255,14 @@ Recommended Reading
 -  SIMD
 
    -  `Whole-Function
-      Vectorization <http://www.cdl.uni-saarland.de/projects/wfv/#header4>`__
+      Vectorization <https://compilers.cs.uni-saarland.de/projects/wfv/#pubs>`__
 
 -  Optimization
 
    -  `Optimizing Pixomatic For Modern x86
       Processors <https://www.drdobbs.com/optimizing-pixomatic-for-modern-x86-proc/184405807>`__
    -  `Intel 64 and IA-32 Architectures Optimization Reference
-      Manual <https://www.intel.com/content/www/us/en/architecture-and-technology/64-ia-32-architectures-optimization-manual.html>`__
+      Manual <https://cdrdv2-public.intel.com/671488/248966_software_optimization_manual.pdf>`__
    -  `Software optimization
       resources <https://www.agner.org/optimize/>`__
    -  `Intel Intrinsics
@@ -273,11 +273,11 @@ Recommended Reading
    -  `LLVM Language Reference
       Manual <https://llvm.org/docs/LangRef.html>`__
    -  `The secret of LLVM C
-      bindings <https://npcontemplation.blogspot.co.uk/2008/06/secret-of-llvm-c-bindings.html>`__
+      bindings <https://npcontemplation.blogspot.com/2008/06/secret-of-llvm-c-bindings.html>`__
 
 -  General
 
    -  `A trip through the Graphics
       Pipeline <https://fgiesen.wordpress.com/2011/07/09/a-trip-through-the-graphics-pipeline-2011-index/>`__
    -  `WARP Architecture and
-      Performance <https://msdn.microsoft.com/en-us/library/gg615082.aspx#architecture>`__
+      Performance <https://learn.microsoft.com/en-us/windows/win32/direct3darticles/directx-warp#warp-architecture-and-performance>`__

docs/drivers/svga3d.rst

@@ -62,8 +62,8 @@ The components involved in this include:
 
 All of these components reside in the guest Linux virtual machine. On
 the host, all you're doing is running VMware
-`Workstation <https://www.vmware.com/products/workstation/>`__ or
-`Fusion <https://www.vmware.com/products/fusion/>`__.
+`Workstation Pro <https://www.vmware.com/products/workstation-pro.html>`__ or
+`Fusion <https://www.vmware.com/products/fusion.html>`__.
 
 Prerequisites
 -------------