poky/bitbake
Richard Purdie 941c5ddd19 bitbake: codeparser: Switch to sha256 from md5
We've reports of hash collision with codeparser. Looking at the way collision
problems occur with md5 and the way our function templating works, I can believe
we may run into issues.

This patch therefore switches to sha256.

Performance wise, parse time could appear to rise by 4s in 374s

Before:

384329 in 2.966s (md5)

After:

349743 in 2.340s (sha256)
34723 in 1.245s (md5)

since we still have md5 used elsewhere in the code, something we should look at
next (using sha256 everywhere is around 5.3s in total)

Unfortunately this does nearly double the size of the codeparser cache file
due to the hash size change.

(Bitbake rev: 4bed7a97198176503fe8c72d8dd7c36b28fc9dd1)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-01-08 11:16:03 +00:00
..
bin bitbake: bitbake: hashserv: Add hash equivalence reference server 2019-01-08 11:16:03 +00:00
contrib bitbake: contrib/dump_cache.py: make it can dump everything 2018-02-14 15:26:03 +00:00
doc bitbake: bitbake-user-manual: Created unique tags for glossary variables. 2018-12-27 13:08:30 +00:00
lib bitbake: codeparser: Switch to sha256 from md5 2019-01-08 11:16:03 +00:00
AUTHORS
ChangeLog
COPYING
HEADER
LICENSE bitbake: lib/bb/siggen: show word-diff for single-line values containing spaces 2017-04-10 23:00:32 +01:00
README bitbake: README: new readme file including main aspects of the project 2017-10-07 23:20:41 +01:00
toaster-requirements.txt bitbake: toaster: bump django version to match build tools 2018-10-18 10:59:26 +01:00

Bitbake
=======

BitBake is a generic task execution engine that allows shell and Python tasks to be run
efficiently and in parallel while working within complex inter-task dependency constraints.
One of BitBake's main users, OpenEmbedded, takes this core and builds embedded Linux software
stacks using a task-oriented approach.

For information about Bitbake, see the OpenEmbedded website:
    http://www.openembedded.org/

Bitbake plain documentation can be found under the doc directory or its integrated
html version at the Yocto Project website:
    http://yoctoproject.org/documentation

Contributing
------------

Please refer to
http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
for guidelines on how to submit patches, just note that the latter documentation is intended
for OpenEmbedded (and its core) not bitbake patches (bitbake-devel@lists.openembedded.org)
but in general main guidelines apply. Once the commit(s) have been created, the way to send
the patch is through git-send-email. For example, to send the last commit (HEAD) on current
branch, type:

    git send-email -M -1 --to bitbake-devel@lists.openembedded.org

Mailing list:

    http://lists.openembedded.org/mailman/listinfo/bitbake-devel

Source code:

    http://git.openembedded.org/bitbake/