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

Add support for pointers larger than 64 bits #1031

Open
FlashSheridan opened this issue Apr 29, 2024 · 5 comments
Open

Add support for pointers larger than 64 bits #1031

FlashSheridan opened this issue Apr 29, 2024 · 5 comments
Labels
memory Memory Model

Comments

@FlashSheridan
Copy link
Contributor

ir/memory.cpp:199 and tools/transform.cpp:904 assert bits_program_pointer <= 64, the former with a comment:

TODO: support pointers larger than 64 bits.

Changing the assertions for this and non-0 address spaces allowed me to test some of our simple IR, but ran into multiple assertion failures (apparently involving null pointers) on more realistic IR. (Discussion at “Add support for non-0 address spaces #877.”)

@Hels15
Copy link

Hels15 commented May 6, 2024

@FlashSheridan Hi, Could you tell me the current state of this issue? I'm looking for contributing opportunities and would appreciate it if you'd be able to give me an update on this. Thank you.

@nunoplopes
Copy link
Member

@Hels15 this is not an easy thing to fix.

@FlashSheridan
Copy link
Contributor Author

@FlashSheridan Hi, Could you tell me the current state of this issue? I'm looking for contributing opportunities and would appreciate it if you'd be able to give me an update on this. Thank you.

I could send you my logs and notes, plus the internal instructions on our wiki for seeking a small amount of wheat among a huge amount of chaff. I can’t claim to have made any significant progress; excerpt: “Finished analyzing pre-death output from Alive2 on the IR from CpuConstraintPoly.sol [largest Solidity contract in era-compiler-tests]. Only two non-trivial validations,” [among 20,422 files]. I agree that it is not an easy issue.

@Hels15
Copy link

Hels15 commented May 6, 2024

@FlashSheridan Hi, Could you tell me the current state of this issue? I'm looking for contributing opportunities and would appreciate it if you'd be able to give me an update on this. Thank you.

I could send you my logs and notes, plus the internal instructions on our wiki for seeking a small amount of wheat among a huge amount of chaff. I can’t claim to have made any significant progress; excerpt: “Finished analyzing pre-death output from Alive2 on the IR from CpuConstraintPoly.sol [largest Solidity contract in era-compiler-tests]. Only two non-trivial validations,” [among 20,422 files]. I agree that it is not an easy issue.

I would highly appreciate that, although as Nuno pointed out before it is quite unlikely that I can contribute something valuable to this topic, if it's not too much of a business feel free to send me those notes, but don't bother too much of it as I'm afraid it's quite "useless" for me at the time. Thank you.

@nunoplopes nunoplopes added the memory Memory Model label May 7, 2024
@FlashSheridan
Copy link
Contributor Author

I would highly appreciate that, …

A couple of days ago I emailed some extracts from the second version of our wiki, to the address for the organization on your GitHub profile. (I have a “mail me” link on the new URL in my GitHub profile, http://flash-sheridan.name. POBox is killing my old URL for life, http://pobox.com/~flash, this month.)

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

No branches or pull requests

3 participants