New: arch/powerpc/mm/mmu_context.o Assembler messages: Error: unrecognized opcode: `dssall' (PowerMac G4)

https://bugzilla.kernel.org/show_bug.cgi?id=215658

Bug ID: 215658
Summary: arch/powerpc/mm/mmu_context.o Assembler messages:
Error: unrecognized opcode: `dssall' (PowerMac G4)
Product: Platform Specific/Hardware
Version: 2.5
Kernel Version: 5.16.12
Hardware: PPC-32
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: PPC-32
Assignee: [email protected]
Reporter: [email protected]
Regression: Yes

Created attachment 300528
--> https://bugzilla.kernel.org/attachment.cgi?id=300528&action=edit
kernel .config (5.16.12, PowerMac G4 DP)

5.16.12 kernel build for my G4 DP on my Talos II fails with:

[...]

  CC      arch/powerpc/mm/init_32.o
  CC      arch/powerpc/mm/pgtable_32.o
  CC      arch/powerpc/mm/pgtable-frag.o
  CC      arch/powerpc/mm/ioremap.o
  CC      arch/powerpc/mm/ioremap_32.o
  CC      arch/powerpc/mm/init-common.o
  CC      arch/powerpc/mm/mmu_context.o

{standard input}: Assembler messages:
{standard input}:30: Error: unrecognized opcode: `dssall'
make[2]: *** [scripts/Makefile.build:287: arch/powerpc/mm/mmu_context.o] Fehler 1
make[1]: *** [scripts/Makefile.build:549: arch/powerpc/mm] Fehler 2
make: *** [Makefile:1846: arch/powerpc] Error 2

This seems to have been introduced by commit d51f86cfd8e378d4907958db77da3074f6dce3ba "powerpc/mm: Switch obsolete dssall to .long"

Reverting this commit fixes the build for my G4.

You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=215658

Christophe Leroy ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #1 from Christophe Leroy ([email protected]) --- This description is puzzling.

Commit d51f86cfd8e3 ("powerpc/mm: Switch obsolete dssall to .long") is not in v5.16.12

For me, applying that commit to v5.16.12 should fix your problem, not the reverse.

You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=215658

Erhard F. ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #2 from Erhard F. ([email protected]) ---
This was Gentoo Sources v5.16.12 not upstream sources. But now I am not able to reproduce it which is even more strange... Also Gentoos' v5.16.13 builds ok.

What I did in the meantime was downgrading to binutils 2.37 (had 2.38 before) and rebuilding the toolchain afterwards.

So this probably was never a bug but an issue with my setup. ;) Closing here.

You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.