Skip to content
This repository was archived by the owner on Nov 11, 2021. It is now read-only.

Conversation

mjz19910
Copy link

@mjz19910 mjz19910 commented Oct 12, 2021

When I was programming the porth.porth program to eventually write the compiled asm to a file.

I encountered a requirement to set the permission mask when using the openat syscall to open a output file for writing.

When I could only pass 3 of the 4 arguments, I ended up with a file I didn't have write permission to open again. The next time I attempted to run the compiled porth compiler, I was denied permission to open the output file.

rexim added 30 commits October 13, 2021 20:33
The strategy is based on check all of the possible execution paths
mjz19910 and others added 7 commits October 25, 2021 17:56
Change the syscall intrinsic the openat macro uses to the 4 argument
syscall intrinsic.

When I was refactoring the porth.porth program to actually write
output to a file, I encountered the inability to set the
permission mask when `openat`ing the out.asm file.
a different program.

Stuff I already did...
Porth, open and write the asm to a file.
Stuff I will work on...
Python, want to figure out constant folding optimization next
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants