esp-idf/components/nvs_flash/src
Ivan Grokhotkov c47cc63489 newlib: change definition of assert for release builds
One common pattern of using assert function looks as follows:
    int ret = do_foo();
    assert(ret == 0);   // which reads as: “do_foo should never fail here, by design”
The problem with such code is that if ‘assert’ is removed by the preprocessor in release build,
variable ret is no longer used, and the compiler issues a warning about this.
Changing assert definition in the way done here make the variable used, from language syntax perspective.
Semantically, the variable is still unused at run time (as sizeof can be evaluated at compile time), so the compiler
can optimize things away if possible.
2017-01-17 00:49:38 +08:00
..
compressed_enum_table.hpp
intrusive_list.h
nvs.hpp
nvs_api.cpp phy_init: reduce the amount of hardwired logic, add coexist init 2016-11-18 20:11:17 +08:00
nvs_item_hash_list.cpp
nvs_item_hash_list.hpp
nvs_page.cpp nvs, spi_flash: handle case when source data is in DROM 2016-11-18 20:11:17 +08:00
nvs_page.hpp
nvs_pagemanager.cpp newlib: change definition of assert for release builds 2017-01-17 00:49:38 +08:00
nvs_pagemanager.hpp
nvs_platform.hpp nvs: allow nvs_flash_init to be called more than once 2016-11-18 20:11:16 +08:00
nvs_storage.cpp nvs: allow nvs_flash_init to be called more than once 2016-11-18 20:11:16 +08:00
nvs_storage.hpp nvs: allow nvs_flash_init to be called more than once 2016-11-18 20:11:16 +08:00
nvs_test_api.h nvs: allow nvs_flash_init to be called more than once 2016-11-18 20:11:16 +08:00
nvs_types.cpp
nvs_types.hpp