mlsanityData to 14 Oct 2026

Unraveling Code Clone Dynamics in Deep Learning Frameworks

arXiv 2404.17046 ↗First posted 25 Apr 2024cs.SE cs.AIcited by 2

Not on the map. Why?

Abstract (arXiv)

Deep Learning (DL) frameworks play a critical role in advancing artificial intelligence, and their rapid growth underscores the need for a comprehensive understanding of software quality and maintainability. DL frameworks, like other systems, are prone to code clones. Code clones refer to identical or highly similar source code fragments within the same project or even across different projects. Code cloning can have positive and negative implications for software development, influencing maintenance, readability, and bug propagation. In this paper, we aim to address the knowledge gap concerning the evolutionary dimension of code clones in DL frameworks and the extent of code reuse across these frameworks. We empirically analyze code clones in nine popular DL frameworks, i.e., TensorFlow, Paddle, PyTorch, Aesara, Ray, MXNet, Keras, Jax and BentoML, to investigate (1) the characteristics of the long-term code cloning evolution over releases in each framework, (2) the short-term, i.e., within-release, code cloning patterns and their influence on the long-term trends, and (3) the file-level code clones within the DL frameworks. Our findings reveal that DL frameworks adopt four distinct cloning trends and that these trends present some common and distinct characteristics. For instance, bug-fixing activities persistently happen in clones irrespective of the clone evolutionary trend but occur more in the "Serpentine" trend. Moreover, the within release level investigation demonstrates that short-term code cloning practices impact long-term cloning trends. The cross-framework code clone investigation reveals the presence of functional and architectural adaptation file-level cross-framework code clones across the nine studied frameworks. We provide insights that foster robust clone practices and collaborative maintenance in the development of DL frameworks.

Key facts. Cited by 2 papers in the map (data through 14 Oct 2026). Builds on 19 of its 98 references that are in the map. First posted on arXiv 25 Apr 2024.

Builds on

19 of 98 references.

References · 19

  1. 2019Taxonomy of Real Faults in Deep Learning Systemscited by 90
  2. 2019A Comprehensive Study on Deep Learning Bug Characteristicscited by 65
  3. 2015SourcererCC: Scaling Code Clone Detection to Big Codecited by 40
  4. 2020Repairing Deep Neural Networks: Fix Patterns and Challengescited by 33
  5. 2022Toward Understanding Deep Learning Framework Bugscited by 26
  6. 2021Silent Bugs in Deep Learning Frameworks: An Empirical Study of Keras and TensorFlowcited by 25
  7. 2023A systematic literature review on source code similarity measurement and clone detection: techniques, applications, and challengescited by 14
  8. 2022On Reporting Performance and Accuracy Bugs for Deep Learning Frameworks: An Exploratory Study from GitHubcited by 7
  9. 2018Automatic Clone Recommendation for Refactoring Based on the Present and the Pastcited by 5
  10. 2021Clones in Deep Learning Code: What, Where, and Why?cited by 5
  11. 2023Common Challenges of Deep Reinforcement Learning Applications Development: An Empirical Studycited by 5
  12. 2023Using a Nearest-Neighbour, BERT-Based Approach for Scalable Clone Detectioncited by 4
7 more
  1. 2021An Exploratory Study on the Introduction and Removal of Different Types of Technical Debtcited by 3
  2. 2016On the Relationship of Inconsistent Software Clones and Faults: An Empirical Studycited by 2
  3. 2022Clone Detection on Large Scala Codebasescited by 2
  4. 2017Scripted GUI Testing of Android Apps: A Study on Diffusion, Evolution and Fragilitycited by 1
  5. 2018Sourcerer's Apprentice and the study of code snippet migrationcited by 1
  6. 2021On the Nature of Code Cloning in Open-Source Java Projectscited by 1
  7. 2023An Empirical Study on Bugs Inside PyTorch: A Replication Studycited by 1

Built on by

Cited by year

Citing papers per year: 2024: 1; 2025: 1.

2 papers.