z00m128 / sjasmplus

98%

master: 98%

LAST BUILD ON BRANCH labels_ph_features_328

branch: labels_ph_features_328

CHANGE BRANCH

x

Reset

• labels_ph_features_328
• 2026_ci_tuning
• ADDTOTRD
• HEAD
• IndentedLabels_298
• IntelHex_288
• PRE-DEFINED_Issue_66_114
• SymbOS_relocate
• Xalior-ci-migration
• add-reproducibility-ci-235
• big_endian_hosts
• ci_freebsd_tuning
• deb_267
• dependabot/github_actions/actions/checkout-6.0.3
• development
• fullpath_experiment
• gen-dfsg-tarball
• janko-jj-master
• lua5.4
• master
• next_version_tidbits
• removal_of_VS_specifics
• sizeof_16
• std_fs_attempt
• std_unordered_map
• substitution_string_glue_257
• unitTestPP
• v1.23.1
• v1.23.1.1

Build # 1586

Build Type

push

cirrus-ci

Committed by ped7g

Commit Message

labels: add physical address/page operators $$$label and $$$$label

Since internally these are tracked for SIZEOF implementation, it's
reasonably easy to surface them to user as cross-over with already
existing $$$ and $$$$ operators.

The label versions are not confined to device mode, but also the logical
results come for regular labels only (for non-DISP the physical address
and page is equal to regular address and page of course, inside DISP
block the physical values show where the machine code landed).

For EQU/DEFL/SMC-offset labels the results are less designed and more
"what happens as implementation side-effect", but they are documented by
adding them to the test, so the user can actually depend on this "logic"
in their own source, in case it is practical for anything.

The only really "unfortunate" behavior is struct-member-label which has
physical address of the whole structure, not the member field, this is
noted in test as "unfortunate" and workaround for more logical physical
address of member expression suggested.

But I think I will not ever change even that, doesn't seem to be worth
the extra complexity of implementation for feature which has probably no
real world use case, and can be easily worked around if really needed.

Coverage Stats

14 of 14 new or added lines in 2 files covered. (100.0%)

10138 of 10372 relevant lines covered (97.74%)

172268.52 hits per line