Avoid generating bindings to simd primitives.

These primitives overlap with C++ macros of the same name in a way that
breaks generated bindings. It is unlikely we need bindings to Rust
primitives in C++, so avoid the issue by excluding the bindings.

PiperOrigin-RevId: 827678631

Author: thunderseethe

cc_bindings_from_rs/generate_bindings/lib.rs

@@ -367,6 +367,13 @@ fn public_paths_by_def_id(
             if stability.is_unstable() {
                 return;
             }
+            // SIMD primitives often have name collisions with SIMD primitives in C++. The C++
+            // primitives are macros, so namespacing does not prevent collision. We expect people
+            // will not need bindings to these primitives, so we exclude them to prevent the
+            // collission.
+            if ["simd_arch", "simd_x86"].contains(&stability.feature.as_str()) {
+                return;
+            }
         }
 
         // Map type aliases to their underlying type.