Milos Gligoric

Milos Gligoric

Auto-generated profile, based on publicly available information

Milos Gligoric

University of Texas at Austin, Austin, USA

Research Focus & Metrics

Academic Career Length

9Years (2018-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
3 September 2019 in Foundations and Trends® in Programming Languages
Verified
Journal Article
Open access
PDF file
TRTalia Ringer
Talia Ringer
KPKarl Palmskog
Karl Palmskog
ISIlya Sergey
Ilya Sergey
MGMilos Gligoric
Milos Gligoric
ZTZachary Tatlock
Zachary Tatlock
Development of formal proofs of correctness of programs can increase actual and perceived reliability and facilitate better understanding of program specifications and their underlying assumptions. Tools supporting such development have been available for over 40 years, but have only recently seen wide practical use. Projects based on construction of machine-checked formal proofs are now reaching an unprecedented scale, comparable to large software projects, which leads to new challenges in proof development and maintenance. Despite its increasing importance, the field of proof engineering is seldom considered in its own right; related theories, techniques, and tools span many fields and venues. This survey of the literature presents a holistic understanding of proof engineering for program correctness, covering impact in practice, foundations, proof automation, proof organization, and practical proof development.

30 November 2023
Verified
Conference Paper
Open access
JZJiyang Zhang
Jiyang Zhang
PNPengyu Nie
Pengyu Nie
JLJunyi Jessy Li
Junyi Jessy Li
MGMilos Gligoric
Milos Gligoric
Many software projects implement APIs and algorithms in multiple programming languages. Maintaining such projects is tiresome, as developers have to ensure that any change (e.g., a bug fix or a new feature) is being propagated, timely and without errors, to implementations in other programming languages. In the world of ever-changing software, using rule-based translation tools (i.e., transpilers) or machine learning models for translating code from one language to another provides limited value. Translating each time the entire codebase from one language to another is not the way developers work. In this paper, we target a novel task: translating code changes from one programming language to another using large language models (LLMs). We design and implement the first LLM, dubbed Codeditor, to tackle this task. Codeditor explicitly models code changes as edit sequences and learns to correlate changes across programming languages. To evaluate Codeditor, we collect a corpus of 6,613 aligned code changes from 8 pairs of open-source software projects implementing similar functionalities in two programming languages (Java and C#). Results show that Codeditor outperforms the state-of-the-art approaches by a large margin on all commonly used automatic metrics. Our work also reveals that Codeditor is complementary to the existing generation-based models, and their combination ensures even greater performance.

27 May 2018
Verified
Conference Paper
Open access
PDF file
KWKaiyuan Wang
Kaiyuan Wang
CZChenguang Zhu
Chenguang Zhu
ACAhmet Celik
Ahmet Celik
JKJongwook Kim
Jongwook Kim
DBDon Batory
Don Batory
MGMilos Gligoric
Milos Gligoric

12 July 2024 in Proceedings of the ACM on Software Engineering
Verified
Journal Article
Open access
ZZZhiqiang Zang
Zhiqiang Zang
FYFu-Yao Yu
Fu-Yao Yu
ATAditya Thimmaiah
Aditya Thimmaiah
ASAugust Shi
August Shi
MGMilos Gligoric
Milos Gligoric
We present LeJit , a template-based framework for testing Java just-in-time (JIT) compilers. Like recent template-based frameworks, LeJit executes a template—a program with holes to be filled—to generate concrete programs given as inputs to Java JIT compilers. LeJit automatically generates template programs from existing Java code by converting expressions to holes, as well as generating necessary glue code (i.e., code that generates instances of non-primitive types) to make generated templates executable. We have successfully used LeJit to test a range of popular Java JIT compilers, revealing five bugs in HotSpot, nine bugs in OpenJ9, and one bug in GraalVM. All of these bugs have been confirmed by Oracle and IBM developers, and 11 of these bugs were previously unknown, including two CVEs (Common Vulnerabilities and Exposures). Our comparison with several existing approaches shows that LeJit is complementary to them and is a powerful technique for ensuring Java JIT compiler correctness.

12 July 2018
Verified
Conference Paper
Open access
PDF file
KPKarl Palmskog
Karl Palmskog
ACAhmet Celik
Ahmet Celik
MGMilos Gligoric
Milos Gligoric

4 April 2019
Verified
Book Chapter
Open access
PDF file
WWWenxi Wang
Wenxi Wang
KWKaiyuan Wang
Kaiyuan Wang
MGMilos Gligoric
Milos Gligoric
SKSarfraz Khurshid
Sarfraz Khurshid
Alloy is a well-known tool-set for building and analyzing software designs and models. Alloy’s key strengths are its intuitive notation based on relational logic, and its powerful analysis engine backed by propositional satisfiability (SAT) solvers to help users find subtle design flaws. However, scaling the analysis to the designs of real-world systems remains an important technical challenge. This paper introduces a new approach, iAlloy, for more efficient analysis of Alloy models. Our key insight is that users often make small and frequent changes and repeatedly run the analyzer when developing Alloy models, and the development cost can be reduced with the incremental analysis over these changes. iAlloy is based on two techniques – a static technique based on a lightweight impact analysis and a dynamic technique based on solution re-use – which in many cases helps avoid potential costly SAT solving. Experimental results show that iAlloy significantly outperforms Alloy analyzer in the analysis of evolving Alloy models with more than 50% reduction in SAT solver calls on average, and up to 7x speedup.