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

Irix compiler rejects byterun/finalise.c #4480

Closed
vicuna opened this issue Jan 17, 2008 · 1 comment
Closed

Irix compiler rejects byterun/finalise.c #4480

vicuna opened this issue Jan 17, 2008 · 1 comment
Labels

Comments

@vicuna
Copy link

vicuna commented Jan 17, 2008

Original bug ID: 4480
Reporter: Christoph Bauer
Status: closed (set by @damiendoligez on 2008-01-17T15:46:20Z)
Resolution: fixed
Priority: normal
Severity: trivial
Version: 3.10.1
Category: ~DO NOT USE (was: OCaml general)
Has duplicate: #4483

Bug description

There is a variable declaration after a statement. No problem for gcc,
but Irixs cc is more restrictive. See below.

Additional information

*** finalise.c.orig Donnerstag, 17. Januar 2008 15:26:52
--- finalise.c Donnerstag, 17. Januar 2008 15:27:45


*** 85,92 ****
Assert (Is_in_heap (final_table[i].val));
if (Is_white_val (final_table[i].val)){
if (Tag_val (final_table[i].val) == Forward_tag){
Assert (final_table[i].offset == 0);
! value fv = Forward_val (final_table[i].val);
if (Is_block (fv) && (Is_young (fv) || Is_in_heap (fv))
&& (Tag_val (fv) == Forward_tag || Tag_val (fv) == Lazy_tag
|| Tag_val (fv) == Double_tag)){
--- 85,93 ----
Assert (Is_in_heap (final_table[i].val));
if (Is_white_val (final_table[i].val)){
if (Tag_val (final_table[i].val) == Forward_tag){

  •       value fv;
          Assert (final_table[i].offset == 0);
    

! fv = Forward_val (final_table[i].val);
if (Is_block (fv) && (Is_young (fv) || Is_in_heap (fv))
&& (Tag_val (fv) == Forward_tag || Tag_val (fv) == Lazy_tag
|| Tag_val (fv) == Double_tag)){

@vicuna
Copy link
Author

vicuna commented Jan 17, 2008

Comment author: @damiendoligez

Thanks for the report. This will be fixed in the next release.

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

No branches or pull requests

1 participant