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

The flambda manual should document "Fatal error: Assignment of a float to a specialised non-float array" #7499

Closed
vicuna opened this issue Mar 3, 2017 · 3 comments
Assignees

Comments

@vicuna
Copy link

vicuna commented Mar 3, 2017

Original bug ID: 7499
Reporter: @gasche
Assigned to: @mshinwell
Status: resolved (set by @mshinwell on 2017-03-03T17:14:08Z)
Resolution: not a bug
Priority: normal
Severity: text
Category: documentation
Related to: #7426

Bug description

This flambda error occurs in existing OCaml programs, where it is not always the sign of an erroneous use of unsafe features. This is a delicate issue and I don't know what guidance to give to users that encounter this error.

The meaning of this error, and how to diagnoze and fix the situation, should be documented in the flambda manual: https://caml.inria.fr/pub/docs/manual-ocaml/flambda.html

Additional information

This error seems occurs with Frama-C for example:
ocaml/opam-repository#8599 (comment)

@vicuna
Copy link
Author

vicuna commented Mar 3, 2017

@vicuna
Copy link
Author

vicuna commented Mar 3, 2017

Comment author: @gasche

For people ending up in this issue as they are looking for documentation: if the program that fails to compile uses objects with a float instance variable, look no further, this is an instance of #7426 which has been fixed upstream in 4.05.

@vicuna
Copy link
Author

vicuna commented Mar 3, 2017

Comment author: @mshinwell

Fatal errors in Flambda are always intended to indicate a bug in the compiler; I don't think they should be documented in the manual. That was the case for #7426 and I very strongly suspect the same issue is responsible for the two reports here, since they both involve variables called "self". The first result on Google for that error message is in fact #7426...

If this error is ever seen on user code when using a compiler with the fix for #7426, even if using unsafe features, another Mantis issue should be opened.

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

2 participants