Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

android_arm32v7a has duplicated labels in assembler .s files #6

Closed
jonahbeckford opened this issue Sep 12, 2024 · 0 comments
Closed

Comments

@jonahbeckford
Copy link
Contributor

jonahbeckford commented Sep 12, 2024

GNU AS (available in NDK23 and earlier) handled the duplicated labels, but clang assembler armclang fails on duplicates.

Reference: https://developer.arm.com/documentation/101754/0622/armclang-Reference/armclang-inline-assembler/Duplication-of-labels-in-inline-assembly-statements
Job: https://github.com/diskuv/dkml-compiler/actions/runs/10825683015/job/30035113740

/usr/bin/env /home/runner/work/dkml-compiler/dkml-compiler/dist/android_arm32v7a-on-linux_x86/opt/mlcross/android_arm32v7a/src/ocaml/support/ocamlcTarget.wrapper -strict-sequence -absname -w +a-4-9-41-42-44-45-48-70 -g -warn-error +A -bin-annot -nostdlib -principal -safe-string -strict-formats  -nolabels -no-alias-deps \
         -o stdlib__Float.cmo -c float.ml
camlinternalAtomic.scamlinternalFormatBasics.s::6094::11: : error: error: symbol '.L116' is already definedsymbol '.L100' is already defined

.L116:.L100:

^^

camlinternalAtomic.s:146:1: error: symbol '.L105' is already defined
.L105:
^
camlinternalAtomic.s:173:1: error: symbol '.L106' is already defined
.L106:
^
camlinternalAtomic.s:202:1: error: symbol '.L108' is already defined
.L108:
^
camlinternalAtomic.s:262:1: error: symbol '.L110' is already defined
.L110:
^
camlinternalAtomic.s:289:1: error: symbol '.L112' is already defined
.L112:
^
camlinternalFormatBasics.s:461:1: error: symbol '.L193' is already defined
.L193:
^
camlinternalFormatBasics.s:863:1: error: symbol '.L280' is already defined
.L280:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant