fa2344
On big-endian machines, a test case looking for the methods _L1D and _E1D
fa2344
in the same scope would fail (see tests/misc/badcode.asl:184).  The names
fa2344
to be compared were being treated as 32-bit ints, and not strings.  Hence,
fa2344
the characters were re-ordered incorrectly, mismatching the assumptions
fa2344
made in the remainder of the function.
fa2344
fa2344
diff --git a/source/compiler/aslanalyze.c b/source/compiler/aslanalyze.c
fa2344
index bf5b37c..11eef08 100644
fa2344
--- a/source/compiler/aslanalyze.c
fa2344
+++ b/source/compiler/aslanalyze.c
fa2344
@@ -461,7 +461,7 @@ ApCheckForGpeNameConflict (
fa2344
 
fa2344
     /* Need a null-terminated string version of NameSeg */
fa2344
 
fa2344
-    ACPI_MOVE_32_TO_32 (Name, &Op->Asl.NameSeg);
fa2344
+    ACPI_MOVE_NAME (Name, &Op->Asl.NameSeg);
fa2344
     Name[ACPI_NAME_SIZE] = 0;
fa2344
 
fa2344
     /*
fa2344
@@ -488,7 +488,7 @@ ApCheckForGpeNameConflict (
fa2344
      * We are now sure we have an _Lxx or _Exx.
fa2344
      * Create the target name that would cause collision (Flip E/L)
fa2344
      */
fa2344
-    ACPI_MOVE_32_TO_32 (Target, Name);
fa2344
+    ACPI_MOVE_NAME (Target, Name);
fa2344
 
fa2344
     /* Inject opposite letter ("L" versus "E") */
fa2344