We used to align destination buffer instead of source buffer for the loop of block copy.
This is a mistake.
Details
- Reviewers
courbet avieira - Commits
- rGaa9db51ef69f: [libc] Align src buffer instead of dst buffer
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Hi Guillaume,
Sorry for the late reply, I was looking at some other things and then holidays happened. I started looking at making some changes to CopyAlignedBlocks just like we discussed earlier. One of them is this one and I noticed this makes the MemcpyUtilsTest.CopyAlignedBlocks fail in libc_string_unittests. Specifically the ones that test destination misalignment. It seems the testing infrastructure keeps track of what bytes were read and written. I checked and making the source the misaligned input and switching the read and written expected traces makes it passs. Which makes sense I guess.
Would be good to make the change at the same time though.
Thx for noticing, it should be good now. I'll move you back to reviewers if you don't mind.
Sure, LGTM. What is the usual convention for Libc reviewing? Should I 'accept revision' if I agree with it even though I'm not a maintainer?
I don't know TBH :-)
I think it's fine if you accept revision even if you're not a maintainer.