wownero/tests/performance_tests/CMakeLists.txt

# Copyright (c) 2014-2022, The Monero Project
#
# All rights reserved.
#
# Redistribution and use in source and binary forms, with or without modification, are
# permitted provided that the following conditions are met:
#
# 1. Redistributions of source code must retain the above copyright notice, this list of
#    conditions and the following disclaimer.
#
# 2. Redistributions in binary form must reproduce the above copyright notice, this list
#    of conditions and the following disclaimer in the documentation and/or other
#    materials provided with the distribution.
#
# 3. Neither the name of the copyright holder nor the names of its contributors may be
#    used to endorse or promote products derived from this software without specific
#    prior written permission.
#
# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
# EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
# THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
# INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
# STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
# THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

set(performance_tests_sources
  main.cpp)

set(performance_tests_headers
  check_tx_signature.h
  check_hash.h
  cn_slow_hash.h
  construct_tx.h
  derive_public_key.h
  derive_secret_key.h
  ge_frombytes_vartime.h
  generate_key_derivation.h
  generate_key_image.h
  generate_key_image_helper.h
  generate_keypair.h
  signature.h
  is_out_to_acc.h
  out_can_be_to_acc.h
  subaddress_expand.h
  range_proof.h
  bulletproof.h
  bulletproof_plus.h
  crypto_ops.h
  sc_reduce32.h
  sc_check.h
  multiexp.h
  multi_tx_test_base.h
  performance_tests.h
  performance_utils.h
  single_tx_test_base.h)

monero_add_minimal_executable(performance_tests
  ${performance_tests_sources}
  ${performance_tests_headers})
target_link_libraries(performance_tests
  PRIVATE
    wallet
    cryptonote_core
    common
    cncrypto
    epee
    ${Boost_CHRONO_LIBRARY}
    ${CMAKE_THREAD_LIBS_INIT}
    ${EXTRA_LIBRARIES})
set_property(TARGET performance_tests
  PROPERTY
    FOLDER "tests")
Copyright: Update to 2022 2022-03-01 11:16:17 +00:00			`# Copyright (c) 2014-2022, The Monero Project`
cmake: put each test executable in its own directory 2014-10-21 17:01:56 +00:00			`#`
			`# All rights reserved.`
			`#`
			`# Redistribution and use in source and binary forms, with or without modification, are`
			`# permitted provided that the following conditions are met:`
			`#`
			`# 1. Redistributions of source code must retain the above copyright notice, this list of`
			`# conditions and the following disclaimer.`
			`#`
			`# 2. Redistributions in binary form must reproduce the above copyright notice, this list`
			`# of conditions and the following disclaimer in the documentation and/or other`
			`# materials provided with the distribution.`
			`#`
			`# 3. Neither the name of the copyright holder nor the names of its contributors may be`
			`# used to endorse or promote products derived from this software without specific`
			`# prior written permission.`
			`#`
			`# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY`
			`# EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF`
			`# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL`
			`# THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,`
			`# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,`
			`# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS`
			`# INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,`
			`# STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF`
			`# THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.`

			`set(performance_tests_sources`
			`main.cpp)`

			`set(performance_tests_headers`
tests: add performance tests for rct signatures 2016-10-08 17:53:31 +00:00			`check_tx_signature.h`
Make difficulty 128 bit instead of 64 bit Based on Boolberry work by: jahrsg <jahr@jahr.me> cr.zoidberg <crypto.zoidberg@gmail.com> 2019-01-31 10:44:08 +00:00			`check_hash.h`
cmake: put each test executable in its own directory 2014-10-21 17:01:56 +00:00			`cn_slow_hash.h`
			`construct_tx.h`
			`derive_public_key.h`
			`derive_secret_key.h`
tests: add performance test for ge_frombytes_vartime At luigi1111's request 2016-10-08 18:34:42 +00:00			`ge_frombytes_vartime.h`
cmake: put each test executable in its own directory 2014-10-21 17:01:56 +00:00			`generate_key_derivation.h`
			`generate_key_image.h`
			`generate_key_image_helper.h`
tests: add performance test for keypair::generate 2016-10-26 21:10:05 +00:00			`generate_keypair.h`
performance_tests: add signature generation/verification 2018-03-16 19:02:55 +00:00			`signature.h`
cmake: put each test executable in its own directory 2014-10-21 17:01:56 +00:00			`is_out_to_acc.h`
Add view tags to outputs to reduce wallet scanning time Implements view tags as proposed by @UkoeHB in MRL issue https://github.com/monero-project/research-lab/issues/73 At tx construction, the sender adds a 1-byte view tag to each output. The view tag is derived from the sender-receiver shared secret. When scanning for outputs, the receiver can check the view tag for a match, in order to reduce scanning time. When the view tag does not match, the wallet avoids the more expensive EC operations when deriving the output public key using the shared secret. 2021-11-15 13:23:53 +00:00			`out_can_be_to_acc.h`
performance_tests: add a test for subaddress expansion 2017-10-22 09:34:17 +00:00			`subaddress_expand.h`
performance_tests: add (Borromean) range proofs 2018-01-05 12:36:32 +00:00			`range_proof.h`
performance_tests: add bulletproofs 2018-01-05 13:10:14 +00:00			`bulletproof.h`
Bulletproofs+ 2020-12-13 00:37:16 +00:00			`bulletproof_plus.h`
performance_tests: add crypto ops 2018-01-05 16:30:24 +00:00			`crypto_ops.h`
performance_tests: sc_check and ge_dsm_precomp 2018-08-08 21:19:57 +00:00			`sc_reduce32.h`
			`sc_check.h`
add Straus multiexp 2018-01-14 23:06:55 +00:00			`multiexp.h`
cmake: put each test executable in its own directory 2014-10-21 17:01:56 +00:00			`multi_tx_test_base.h`
			`performance_tests.h`
			`performance_utils.h`
			`single_tx_test_base.h)`

Add RELINK_TARGETS, monero_add_target_no_relink and use monero_add_executable/monero_add_library where possible (mj-xmr) Add monero_add_minimal_executable and use in tests This is done in order not to have to relink targets, when just an .so changed, but not its interface. 2020-10-26 19:53:21 +00:00			`monero_add_minimal_executable(performance_tests`
cmake: put each test executable in its own directory 2014-10-21 17:01:56 +00:00			`${performance_tests_sources}`
			`${performance_tests_headers})`
			`target_link_libraries(performance_tests`
cmake: transitive deps and remove deprecated LINK_* Keep the immediate direct deps at the library that depends on them, declare deps as PUBLIC so that targets that link against that library get the library's deps as transitive deps. Break dep cycle between blockchain_db <-> crytonote_core. No code refactoring, just hide cycle from cmake so that it doesn't complain (cycles are allowed only between static libs, not shared libs). This is in preparation for supproting BUILD_SHARED_LIBS cmake built-in option for building internal libs as shared. 2016-09-17 17:59:29 +00:00			`PRIVATE`
performance_tests: add a test for subaddress expansion 2017-10-22 09:34:17 +00:00			`wallet`
cmake: put each test executable in its own directory 2014-10-21 17:01:56 +00:00			`cryptonote_core`
			`common`
changed crypto to cncrypto so it generated libcncrypto fix a cmakelist 2017-05-21 06:21:17 +00:00			`cncrypto`
Change logging to easylogging++ This replaces the epee and data_loggers logging systems with a single one, and also adds filename:line and explicit severity levels. Categories may be defined, and logging severity set by category (or set of categories). epee style 0-4 log level maps to a sensible severity configuration. Log files now also rotate when reaching 100 MB. To select which logs to output, use the MONERO_LOGS environment variable, with a comma separated list of categories (globs are supported), with their requested severity level after a colon. If a log matches more than one such setting, the last one in the configuration string applies. A few examples: This one is (mostly) silent, only outputting fatal errors: MONERO_LOGS=:FATAL This one is very verbose: MONERO_LOGS=:TRACE This one is totally silent (logwise): MONERO_LOGS="" This one outputs all errors and warnings, except for the "verify" category, which prints just fatal errors (the verify category is used for logs about incoming transactions and blocks, and it is expected that some/many will fail to verify, hence we don't want the spam): MONERO_LOGS=:WARNING,verify:FATAL Log levels are, in decreasing order of priority: FATAL, ERROR, WARNING, INFO, DEBUG, TRACE Subcategories may be added using prefixes and globs. This example will output net.p2p logs at the TRACE level, but all other net logs only at INFO: MONERO_LOGS=:ERROR,net:INFO,net.p2p:TRACE Logs which are intended for the user (which Monero was using a lot through epee, but really isn't a nice way to go things) should use the "global" category. There are a few helper macros for using this category, eg: MGINFO("this shows up by default") or MGINFO_RED("this is red"), to try to keep a similar look and feel for now. Existing epee log macros still exist, and map to the new log levels, but since they're used as a "user facing" UI element as much as a logging system, they often don't map well to log severities (ie, a log level 0 log may be an error, or may be something we want the user to see, such as an important info). In those cases, I tried to use the new macros. In other cases, I left the existing macros in. When modifying logs, it is probably best to switch to the new macros with explicit levels. The --log-level options and set_log commands now also accept category settings, in addition to the epee style log levels. 2017-01-01 16:34:23 +00:00			`epee`
cmake: fix up link lines 2014-10-24 19:30:57 +00:00			`${Boost_CHRONO_LIBRARY}`
			`${CMAKE_THREAD_LIBS_INIT}`
cmake: put each test executable in its own directory 2014-10-21 17:01:56 +00:00			`${EXTRA_LIBRARIES})`
			`set_property(TARGET performance_tests`
			`PROPERTY`
			`FOLDER "tests")`