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

armv5te code generation bug: shift expression expected -- `subs r0,r3,#4294967296' #6613

Closed
vicuna opened this issue Oct 13, 2014 · 4 comments

Comments

@vicuna
Copy link

vicuna commented Oct 13, 2014

Original bug ID: 6613
Reporter: @whitequark
Status: resolved (set by @xavierleroy on 2014-10-16T07:31:51Z)
Resolution: suspended
Priority: normal
Severity: feature
Version: 4.02.1+dev
Target version: 4.02.2+dev / +rc1
Category: ~DO NOT USE (was: OCaml general)
Related to: #4303 #5737 #6266
Monitored by: @gasche

Bug description

Build log:

/home/whitequark/.opam/local/bin/ocamlrun ../ocamlopt -strict-sequence -w +33..39 -g -warn-error A -bin-annot -nostdlib -safe-string ./Compflags camlinternalOO.cmx -c camlinternalOO.ml
/tmp/camlasmc9f0c3.s: Assembler messages:
/tmp/camlasmc9f0c3.s:1565: Error: shift expression expected -- `subs r0,r3,#4294967296'
File "camlinternalOO.ml", line 1:
Error: Assembler error, input left in file /tmp/camlasmc9f0c3.s

Additional information

I believe this should be fixed in 4.02.1 as well.

@vicuna
Copy link
Author

vicuna commented Oct 13, 2014

Comment author: @whitequark

Hm, I think this may be the result of running 64-bit ocamlrun on 32-bit bytecode ocamlopt. I will confirm a bit later.

@vicuna
Copy link
Author

vicuna commented Oct 13, 2014

Comment author: @xavierleroy

Indeed, this problem is typical of cross-compiling for a 32-bit platform from a 64-bit host, which is not supported yet. You can do ARM cross compilation but need to build OCaml in 32-bit mode. (There are hints on how to do this in the INSTALL file of the distribution.)

@vicuna
Copy link
Author

vicuna commented Oct 13, 2014

Comment author: @whitequark

This really should fail an assertion or something, as the current behavior is rather confusing, so keeping this issue open. I'm not sure how exactly to fix this, though.

@vicuna
Copy link
Author

vicuna commented Oct 16, 2014

Comment author: @xavierleroy

Better support for cross-compilation is on the mid to long-term agenda.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant