1 On big-endian machines, a test case looking for the methods _L1D and _E1D
3 From: Al Stone <ahs3@redhat.com>
5 in the same scope would fail (see tests/misc/badcode.asl:184). The names
6 to be compared were being treated as 32-bit ints, and not strings. Hence,
7 the characters were re-ordered incorrectly, mismatching the assumptions
8 made in the remainder of the function.
10 source/compiler/aslanalyze.c | 4 ++--
11 1 file changed, 2 insertions(+), 2 deletions(-)
13 Index: acpica-unix2-20161222/source/compiler/aslanalyze.c
14 ===================================================================
15 --- acpica-unix2-20161222.orig/source/compiler/aslanalyze.c
16 +++ acpica-unix2-20161222/source/compiler/aslanalyze.c
17 @@ -461,7 +461,7 @@ ApCheckForGpeNameConflict (
19 /* Need a null-terminated string version of NameSeg */
21 - ACPI_MOVE_32_TO_32 (Name, &Op->Asl.NameSeg);
22 + ACPI_MOVE_NAME (Name, &Op->Asl.NameSeg);
23 Name[ACPI_NAME_SIZE] = 0;
26 @@ -488,7 +488,7 @@ ApCheckForGpeNameConflict (
27 * We are now sure we have an _Lxx or _Exx.
28 * Create the target name that would cause collision (Flip E/L)
30 - ACPI_MOVE_32_TO_32 (Target, Name);
31 + ACPI_MOVE_NAME (Target, Name);
33 /* Inject opposite letter ("L" versus "E") */