Repository navigation
Toolchain content from TuKo1982's 68080 optimisation guide - #11
Merged
Merged
Conversation
Split section 9 of the guide into toolchain/: vasm and GCC pitfalls, libnix traps, calling assembler from GCC, and a best practice on GCC code generation for the 68080. Warn about vasm 2.0f's PC-relative destinations in vasm-assembler.md (option b), explain why -m68881 is needed for FPU code, list the open GCC fixes (ApolloCrossDev PR #5 and #7), and note that the planned LineA code generation would not run on current cores. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Second content PR from TuKo1982's "68080 compilation and optimisation guide": section 9 (toolchain). New files:
owner: TuKo1982,origin: ai-assisted,status: draft.New files
toolchain/pitfalls/:vasm-pc-relative-destination: vasm-m68080rewrites absolute destinations into PC-relative ones, which the 68080 miscomputes after a full-extension source. Option b as agreed: keep the standard options, add the warning and a detection step. The vasm author has been informed.vasm-68080-encoding-issues:add.l #imm,En,add.l b1,d0→$71F1;.s→.s+;loadat the top of a file.gcc-bbb-autoinc: ApolloCrossDev PR Pillar-first content structure and document intake #5, still open.gcc-dbra-address-register-loop: ApolloCrossDev PR Document intake: 68080 Programmer's Reference Manual #7, still open.gcc-stackswap-defer-popfloat-settings-mismatch:-m68080alone is soft-float;-m68881gives hard float;-nostartfileslibraries.gcc-misc-traps:-mtune=68060, NULL writes,-O3.libnix-and-header-trapscalling-assembler-from-gcctoolchain/best-practices/:gcc-code-generation-for-68080Updated files
vasm-assembler.md:Compilers/_archives/vasm/vasm.tar.tar,vasm.c);-no-opt,-L,-devpacandmachine ac68080.c-compiler-options.md:-m68881is required;-O3gives no gain;-mtune=68060;-lmforsprintf.compiler-variants.md:mov3q/clr.q/movs/movzgeneration would produce LineA instructions that only run on cores 10280–10904.core/pitfalls/pc-relative-destination.md: links to the new toolchain pitfall.For the maintainers
-m68080 -m68881= hard float is based on the GCC source (m68k.c: no 680x0 CPU option setsFL_68881for AmigaOS). As agreed, it still needs a test build to validate.compiler-variants.mdwith the version that contains the fix.Knowledge base files relied on
toolchain/(existing files)core/pitfalls/bank-prefix-pitfalls.md,core/pitfalls/pc-relative-destination.md,core/pitfalls/ammx-pc-relative-source.md🤖 Generated with Claude Code