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

Optimization issue #1

Closed
OhGodAPet opened this issue May 20, 2014 · 3 comments
Closed

Optimization issue #1

OhGodAPet opened this issue May 20, 2014 · 3 comments

Comments

@OhGodAPet
Copy link

This isn't the place for this, but I could find no other way to contact you, since you're never on IRC. I've been trying to optimize the aesb_pseudo_round_mut() code, but it seems obfuscated, and I'm not entirely clear on what it does. I attempted to replace it with this linux only code:

http://pastebin.com/qczpTnjY

but it failed - hashing, yet not submitting valid shares.

@lucasjones
Copy link
Owner

I made some changes your code, let me know how this works for you.

http://pastebin.com/haB7FsWb

@OhGodAPet
Copy link
Author

I think this commit causes a bad pointer to be passed to aesb_pseudo_round_mut(). Suddenly, the optimizations that worked before segfault when moving the data pointed at by rdi into xmm1.

927ecbe

Neeeeever mind, I'm an idiot. I have another optimization idea, but first, I have to figure out why it's now crashing in fast_aesb_single_round(). Segfaults... yet gdb can read the address just fine...

@OhGodAPet
Copy link
Author

Got it. You fuck the alignment in that commit. Changing it to 16 fixes the issue!

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

No branches or pull requests

2 participants