24 Commits (0bdbd108d814f33c2d130077bc4b0bd20673b56d)

Author	SHA1	Message	Date
Sarang Noether	0bdbd108d8	Bulletproofs+	3 years ago
SomaticFanatic	5ef0607da6	Update copyright year to 2020 ... Update copyright year to 2020	4 years ago
moneromooo-monero	91f4c7f45f	Make difficulty 128 bit instead of 64 bit ... Based on Boolberry work by: jahrsg <jahr@jahr.me> cr.zoidberg <crypto.zoidberg@gmail.com>	5 years ago
binaryFate	1f2930ce0b	Update 2019 copyright	5 years ago
moneromooo-monero	c415df97bd	performance_tests: sc_check and ge_dsm_precomp	6 years ago
moneromooo-monero	cb9ecab197	performance_tests: add signature generation/verification	6 years ago
moneromooo-monero	939bc22332	add Straus multiexp	6 years ago
moneromooo-monero	112f32f068	performance_tests: add crypto ops	6 years ago
moneromooo-monero	f5d7b9933a	performance_tests: add bulletproofs	6 years ago
moneromooo-monero	1aa10c4364	performance_tests: add (Borromean) range proofs	6 years ago
xmr-eric	18216f19dd	Update 2018 copyright	6 years ago
moneromooo-monero	dc64263155	performance_tests: add a test for subaddress expansion	6 years ago
Gentian	4b932ff314	changed crypto to cncrypto so it generated libcncrypto ... fix a cmakelist	7 years ago
Riccardo Spagni	c3599fa7b9	update copyright year, fix occasional lack of newline at line end	7 years ago
moneromooo-monero	5833d66f65	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.	7 years ago
moneromooo-monero	56b07f7b89	tests: add performance test for keypair::generate	8 years ago
moneromooo-monero	d8eae67ef2	tests: add performance test for ge_frombytes_vartime ... At luigi1111's request	8 years ago
moneromooo-monero	1eaa3e8040	tests: add performance tests for rct signatures	8 years ago
redfish	e1c7af35d4	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.	8 years ago
Riccardo Spagni	de03926850	updated copyright year	8 years ago
Riccardo Spagni	f4b69d553a	year updated in license	9 years ago
Ben Boeckel	01895dd067	cmake: fix up link lines	10 years ago
Ben Boeckel	7d708e4223	cmake: support 2.8.7 ... Older versions of CMake support LINK_{PUBLIC,PRIVATE} while newer versions prefer PUBLIC and PRIVATE instead, but still support the LINK_ prefix.	10 years ago
Ben Boeckel	7bfcffadb9	cmake: put each test executable in its own directory	10 years ago