Papers › A comprehensive review of Binary Neural Network

A comprehensive review of Binary Neural Network

11 Oct 2021arXiv:2110.06804archive 2025-07-28

Chunyu Yuan, Sos S. Agaian

Deep learning (DL) has recently changed the development of intelligent systems and is widely adopted in many real-life applications. Despite their various benefits and potentials, there is a high demand for DL processing in different computationally limited and energy-constrained devices. It is natural to study game-changing technologies such as Binary Neural Networks (BNN) to increase deep learning capabilities. Recently remarkable progress has been made in BNN since they can be implemented and embedded on tiny restricted devices and save a significant amount of storage, computation cost, and energy consumption. However, nearly all BNN acts trade with extra memory, computation cost, and higher performance. This article provides a complete overview of recent developments in BNN. This article focuses exclusively on 1-bit activations and weights 1-bit convolution networks, contrary to previous surveys in which low-bit works are mixed in. It conducted a complete investigation of BNN's development -from their predecessors to the latest BNN algorithms/techniques, presenting a broad design pipeline and discussing each module's variants. Along the way, it examines BNN (a) purpose: their early successes and challenges; (b) BNN optimization: selected representative works that contain essential optimization techniques; (c) deployment: open-source frameworks for BNN modeling and development; (d) terminal: efficient computing architectures and devices for BNN and (e) applications: diverse applications with BNN. Moreover, this paper discusses potential directions and future research opportunities in each section.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 14 code samples harvested from 1 repository linked to this paper: 11 ran (of which 0 constructed an object rather than computing a result; 11 with no instrument failure: 0 honoured, 0 violated, 11 with no contract checked; 0 where Syntology's instrument failed) · 3 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 14 samples from 1 repository, 11 ran (11 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-24 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

hpi-xnor/BMXNet-v2 officialmentioned in papermxnetApache-2.0Syntology: 14 samples, 11 ran (0 instrument-failed) · 3 unverified report
pminhtam/xnor_conv_pytorch_extension pytorchSyntology: not harvested report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

14 samples harvested: 11 ran (of which 0 constructed an object rather than computing a result; 11 with no instrument failure: 0 honoured, 0 violated, 11 with no contract checked; 0 where Syntology's instrument failed) · 3 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

11ran
3unverified

Licence: 14 of the 14 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from hpi-xnor/BMXNet-v2. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

hpi-xnor/BMXNet-v2 official repository 14 samples, 11 ran (0 instrument-failed) · 3 unverified
c_array in 8 papers amalgamation/python/mxnet_predict.py ran Apache-2.0 recorded; this copy not marked cleared · pointer only · 3bc3ed8fa916a182 · report fixture: signature ctype:callable/0/?, values:list/1/int · returned c_int_Array_5 · level recorded 2026-09-25
c_str in 5 papers amalgamation/python/mxnet_predict.py ran Apache-2.0 recorded; this copy not marked cleared · pointer only · 313d72408f5f6086 · report fixture: signature string:str/0/str · returned c_char_p · level recorded 2026-09-25
classproperty python/mxnet/base.py ran Apache-2.0 recorded; this copy not marked cleared · pointer only · 47ebd1622534322e · report fixture: signature func:classmethod/0/? · returned _MXClassPropertyDescriptor · level recorded 2026-09-24
clip in 31 papers dev_menu.py ran fingerprinted Apache-2.0 recorded; this copy not marked cleared · pointer only · b15eee57aa63b7dd · report fixture: signature x:int/0/int, mini:int/0/int, maxi:int/0/int · returned int · level recorded 2026-09-24
do_checkpoint python/mxnet/callback.py ran Apache-2.0 recorded; this copy not marked cleared · pointer only · df77b3eca6bd676b · report fixture: signature prefix:str/0/str, period:int/0/int · returned function · level recorded 2026-09-25
get_docker_tag ci/build.py ran fingerprinted Apache-2.0 recorded; this copy not marked cleared · pointer only · 673cc3400c21de38 · report fixture: signature platform:str/0/str, registry:str/0/str · returned str · level recorded 2026-09-24
get_dockerfile ci/build.py ran fingerprinted Apache-2.0 recorded; this copy not marked cleared · pointer only · ebcf98b1c05abe47 · report fixture: signature platform:str/0/str, path:str/0/str · returned str · level recorded 2026-09-24
log_train_metric python/mxnet/callback.py ran Apache-2.0 recorded; this copy not marked cleared · pointer only · 82771a0ac4ead3ae · report fixture: signature period:int/0/int, auto_reset:bool/0/bool · returned function · level recorded 2026-09-24
module_checkpoint python/mxnet/callback.py ran Apache-2.0 recorded; this copy not marked cleared · pointer only · 4950353b99f3413d · report fixture: signature mod:callable/0/?, prefix:str/0/str, period:int/0/int, save_optimizer_states:bool/0/bool · returned function · level recorded 2026-09-25
record in 8 papers python/mxnet/autograd.py ran Apache-2.0 recorded; this copy not marked cleared · pointer only · b86308bc3bc53b49 · report fixture: signature train_mode:bool/0/bool · returned _RecordingStateScope · level recorded 2026-09-25
retry in 14 papers ci/util.py ran Apache-2.0 recorded; this copy not marked cleared · pointer only · a0b139cbfc78247f · report fixture: signature target_exception:callable/0/?, tries:int/0/int, delay_s:int/0/int, backoff:int/0/int · returned function · level recorded 2026-09-24
set_recording python/mxnet/autograd.py unverified Apache-2.0 recorded; this copy not marked cleared · pointer only · 84a2b5addc51f455 · report
set_training python/mxnet/autograd.py unverified Apache-2.0 recorded; this copy not marked cleared · pointer only · 565479a708f0d1c6 · report
with_metaclass python/mxnet/base.py unverified Apache-2.0 recorded; this copy not marked cleared · pointer only · 05550ef10b65470b · report

Tasks

BinarizationQuantization

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Convolution

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections