Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
CallASWI CallASWI
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Labels
    • Labels
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • RiscOS
    • SSources
    • UUtilities
  • Patches
  • CallASWICallASWI
  • Merge requests
  • !1

Merged
Created Jul 29, 2021 by Jeffrey Lee@jleeDeveloper

Re-sync s.CPUFeatures with the kernel version

  • Overview 0
  • Commits 1
  • Changes 1

This fixes a build error (due to CPUFeature_Max being increased beyond 64 in RiscOS/Sources/Kernel!55 (merged)), and ensures the correct values are reported for the new flags.

Also, add a check to ensure that any addition of new flags will result in a build failure. CallASWI blindly claims that it reports the correct value for all flags, even ones it doesn't contain explicit code for. So if new flags are added which need to be "true" on old CPUs (like CP15_DFAR_DFSR_writable), CallASWI would mistakenly report a "false" value. By forcing a build failure whenever new flags are added to the kernel, we should get some good protection against this kind of mistake.

Admin: Builds, untested.

Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: KernelSync