summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorLines
2023-03-25Update README.mdJuan Gómez Luna-0/+3
2023-03-25Update README.mdJuan Gómez Luna-2/+29
2022-02-23Merge pull request #5 from grb72t3yde/mainJuan Gómez Luna-36/+39
bs_bug_fix: Fix unaligned MRAM reads and boundary case handlings in BS benchmark
2022-02-02Merge pull request #6 from grb72t3yde/fix-README-typoJuan Gómez Luna-2/+2
documentation: Fix typo
2021-12-26documentation: Fix typoYun-Ze Li-2/+2
Signed-off-by: Yun-Ze Li <p76091292@gs.ncku.edu.tw>
2021-12-26documentation: Fix typoYun-Ze Li-2/+2
Signed-off-by: Yun-Ze Li <p76091292@gs.ncku.edu.tw>
2021-12-23bs_refactor: Remove printf for loggingYun-Ze Li-8/+2
Signed-off-by: Yun-Ze Li <p76091292@gs.ncku.edu.tw>
2021-12-23bs_refactor: Remove redundant linesYun-Ze Li-7/+4
This commit reduce redundant lines for calculating `current_mram_block_addrA`. Signed-off-by: Yun-Ze Li <p76091292@gs.ncku.edu.tw>
2021-12-23bs_bug_fix: Modify boundary case handlings in BSYun-Ze Li-41/+38
Current boundary case handling may discard some numbers obliged to be compared with `searching_for`, which in my opinion can result in false positives (BS fails to identify the number which is indeed in the input array). This commit changed the boundary check condition to `if(current_mram_block_addr_A < start_mram_block_addr_A + BLOCK_SIZE)`, where the expression returns true if and only if the length of the range [start_mram_block_addr_A, end_mram_block_addr_A) has become smaller than 2*BLOCK_SIZE. When this happens, we can then finalize the BS result by checking if `searching_for` exists within [start_mram_block_addr_A, end_mram_block_addr_A) without overlooking any number that should be checked. Signed-off-by: Yun-Ze Li <p76091292@gs.ncku.edu.tw>
2021-12-23bs_bug_fix: Make MRAM reads 8-byte alignedYun-Ze Li-0/+15
Current implementation does not guarantee that `current_mram_block_addr_A` is 8-byte aligned before using it as the start address of `mram_read`s. This commit makes `current_mram_block_addr_A` 8-byte aligned whenever we try to use it for a MRAM read by `current_mram_block_addr_A &= WORD_MASK`, which will clear the unaligned bytes. Signed-off-by: Yun-Ze Li <p76091292@gs.ncku.edu.tw>
2021-12-11Merge pull request #4 from intheRain07/mainJuan Gómez Luna-17/+44
gemv_bug_fix
2021-11-16Merge pull request #1 from intheRain07/intheRain07-patch-1intheRain07-17/+44
gemv_bug_fix_2.1
2021-11-16gemv_bug_fix_2.1intheRain07-1/+1
2021-11-16gemv_bug_fix2.0intheRain07-17/+44
2021-10-18Merge pull request #2 from joaodinissf/mainJuan Gómez Luna-6/+6
Replace the deprecated .iteritems() with .items()
2021-10-08Replace the deprecated .iteritems() with .items()João Dinis Ferreira-6/+6
The `.iteritems()` method was [removed](https://docs.python.org/3/library/2to3.html#2to3fixer-dict) in Python 3. The direct replacement is `.items()` (which is backwards-compatible with Python 2). This change means that the execution scripts `run_*.py` fail on Python 3. This commit provides Python 3 compatibility without compromising Python 2 execution. See, for reference: - https://github.com/saltstack-formulas/openssh-formula/issues/48 - https://stackoverflow.com/questions/10458437/what-is-the-difference-between-dict-items-and-dict-iteritems-in-python2
2021-06-16PrIM -- first commitJuan Gomez Luna-2/+70200076
2021-04-09Initial commitJuan Gómez Luna-0/+2
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-30 20:56:08 +0000