* Run C tests on all platforms
* Don't install llvm on mac & add windows define
* Update blst settings for windows
* Install msvc on windows
* Don't specify blst as a library
* Try including -lmingw32
* Clean up makefile & test setting target
* Try using gcc for windows
* Don't treat warnings as errors on windows
* Test upping stack size
* Ignore some tasks on windows
* Clean up some things
* Fix indentations
* Delete extra blank line
* More organization
* Remove windows check around sanitize
* Move XCRUN initialization back to top
* Move extra sanitize cflags out like the others
* Intentionally fail to compile with a FIELD_ELEMENTS_PER_BLOB value that is not a power of 2.
We do not want to support or maintain this case, so let us be explicit about it.
* Update src/c_kzg_4844.h
Co-authored-by: Justin Traglia <95511699+jtraglia@users.noreply.github.com>
* Update src/c_kzg_4844.h
Co-authored-by: Justin Traglia <95511699+jtraglia@users.noreply.github.com>
---------
Co-authored-by: George Kadianakis <desnacked@riseup.net>
Co-authored-by: Justin Traglia <95511699+jtraglia@users.noreply.github.com>
* modify directory structure to isolate the generated bindings
* add a lib.rs file
* move deref impls to the extension file
* remove unused types from generated bindings
* cleanup new lines to reduce diff noise
* reorder definitions to reduce diff noise
* move sync and send impls to the extension file
* generate bindings
* blacklist used bindings; create snapshots dir to ensure freshness in the future
* fix typo. Ty @pawanjay176
* run cargo build after merge
* custom impl for KZGCommitment and KZGProof
* final touches
VLA's are prone to cause (silent!) stack overflows and a potential cause of security vulns.
While the usage pattern is probably safe in our context, changing to a more robust solution seems prudent.
* Documentation update
* Documentation for division. Note that the doc says that the behaviour for a/0 is unspecified. Feel free to change.
* Add some Documentation. This fixes item #3 in https://hackmd.io/@6iQDuIePQjyYBqDChYw_jg/ByXAsi21h
* Moved documentation remark for doxygen @remark to in-code remark. The remark is not useful for API-documentation (it refers to a macro that is not part of the API).
* More verbose comment for bit_reversal_permutation.
* doxygen comment parameter name did not match variable name. Fix this.
* Remove parameter n from doxygen comment of compute_challenge, as there is no such argument.
This fixes#4 in https://hackmd.io/@6iQDuIePQjyYBqDChYw_jg/ByXAsi21h
* In compute_kzg_proof_impl, document the role of the m variable that is used to indicate whether the evaluation point is one of the interpolation points.
* Run `make format`
* Improve multiline comments from `make format` in middle of the code
---------
Co-authored-by: George Kadianakis <desnacked@riseup.net>
Justin Traglia
Matthew Keil
George Kadianakis
Gottfried Herold
Divma
Stefan Bratanov
andri lim
Ruben Buniatyan
Alexey