-
Notifications
You must be signed in to change notification settings - Fork 24
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 Make.win32 -fcommon, define u64int, sync libsec, libmp, libauthsrv with Plan 9, define usize, add chacha20, libsec: add mising \ #16
Conversation
Thanks. I'm looking at it. |
I removed |
Oh, I see there are more changes in this repo vs Plan 9 versions(not that many) I just copied the libs. I could merge and force push I think. |
Overall, it looks good. Thank your for working on this. Could you rename |
Ok, changed libsec commit message, left |
I think it's probably better to add |
I took the flag from here https://github.com/golang/go/blob/ceb95ea6aef52c1fb472d3539c6ef68670778b5b/src/cmd/dist/build.c#L482, not sure if it applies to Plan 9, and I think it's preferable to have identical copies in drawterm and Plan 9. If I were to add |
plan9port removes them completely https://github.com/9fans/plan9port/blob/master/include/mp.h#L137 or comments them out https://github.com/9fans/plan9port/blob/master/include/mp.h#L151, I understand your argument of |
Shall we go with consistency then? |
Although, not all them were |
If you prefer |
Or just live with the warnings. |
The pragma are meant to be interpreted by the Plan 9 C compiler only. I'm not very comfortable keeping them, risking to be handled by the GCC preprocessor, which could lead to side effects. Either deleting them or |
Ok, I'll probably |
Ok, |
Hmm... this might require merging 93a43be |
I don't understand which (if any of the patches) to |
I see block files are done in assembly, I added the C versions 15a79f4#diff-ede5614f90d7b8d84cda78003b911a92e627073420f71965b843c0c4bbab4921R50 for |
1c8b499#diff-60bc2862e39ce285a55d63a7f349f7eb7e5724d0f1bc0baa0cc18a28e0ff5936 this affects |
1125f09#diff-ba43ca4048f51025813c140fdcc7f53f77817dd416f1aa445900c524e5090b86L1 affects |
Merging is always complicated because you have to compare two pieces of code that evolved independently. |
I assume they started from the same sources, and I assume the idea was for them to be sync-ed, if so, they don't seem to have a lot of changes between them. Please take a look at |
For that kind of changes, you have to re-apply the changes Russ did on your |
Yup, exactly! Doesn't seem hard! :) |
Add ChaCha20 stream cipher (RFC7539). http://9legacy.org/9legacy/patch/libsec-chacha.diff
Ok ,merged, patches for 9legacy if interested.
Now, I really don't want to write |
Please review this also, if I didn't miss anything when merging repo changes (I don't think so), it's fine to merge now, except for the asm version of |
Thanks. I'll will do a final review. |
Perhaps you might consider merging to a separate branch for now until everything is complete? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think your changes are ready to be merged on the main
branch.
You will be able to open new PRs for the remaining changes.
@@ -51,7 +51,7 @@ OFILES=\ | |||
sha2block64.$O\ | |||
sha2_128.$O\ | |||
sha2block128.$O\ | |||
smallprimes.$O | |||
smallprimes.$O\ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not necessary, but it doesn't harm.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess I preferred single line diffs as I have to add more stuff there. Your call!
I'm ready to merge into |
Ok to merge! |
I think this also closes #12 |
No description provided.