From 4181f72e3e689c929d3f988d7a9d4051bc3b9547 Mon Sep 17 00:00:00 2001 From: "M. Barbosa" Date: Fri, 14 Aug 2026 17:43:14 -0300 Subject: [PATCH 1/2] fix --- SCAM2026/index.html | 32 +++++++++++++++++--------------- 1 file changed, 17 insertions(+), 15 deletions(-) diff --git a/SCAM2026/index.html b/SCAM2026/index.html index ea889c9..6712510 100644 --- a/SCAM2026/index.html +++ b/SCAM2026/index.html @@ -387,20 +387,22 @@

A Quantitative Characterization of Semantic

Abstract

-

Collaborative software development relies on automated merge tools, but parallel contributions can - introduce dynamic semantic conflicts that alter program behavior without triggering textual merge conflicts. - Different techniques can be used to detect these conflicts, including testing, dynamic analysis, and static - analysis. However, the prevalence, structural characteristics, and distribution of these semantic conflicts - remain largely unexplored at scale. To address this gap, we establish a catalog of topological structures - that characterize recurring structural patterns of semantic conflicts. We conduct an empirical study to - quantify the occurrence of these structures in practice, using interprocedural static analysis on a large - benchmark comprising 907 java merge scenarios where both developers modified the same method from - open-source GitHub repositories. Our results reveal a structural dichotomy: while CF conflicts concentrate - overwhelmingly in fully local topologies (90.4\% start and end in the same file), DF and OA conflicts - exhibit highly divergent behavior, with multi-file topologies accounting for 60.3\% and 46.7\% of their - respective instances. These findings provide actionable guidance for configuring static analysis tools, - demonstrating that fast intraprocedural analysis is sufficient to detect the vast majority of CF conflicts, - whereas deeper interprocedural analysis is essential to uncover DF and OA conflicts.

+

+ Collaborative software development relies on automated merge tools, but parallel contributions can introduce + dynamic semantic conflicts that alter program behavior without triggering textual merge conflicts. Different + techniques can be used to detect these conflicts including testing, dynamic analysis, and static analysis. + However, the prevalence, structural characteristics, and distribution of these semantic conflicts remain + largely unexplored at scale. To address this gap, we establish a catalog of topological structures that + characterize recurring structural patterns of semantic conflicts. We conduct an empirical study to quantify + the occurrence of these structures in practice, using interprocedural static analysis on a large benchmark + comprising 907 Java merge scenarios from open-source GitHub repositories, where the merged branches modify + the same method. Our results reveal a structural dichotomy: while CF conflicts appear mostly in fully local + topologies (90.4% start and end in the same file), DF and OA conflicts appear in multi-file topologies far + more often, accounting for 60.3% and 46.7% of their respective instances. These findings provide actionable + guidance for configuring static analysis tools, demonstrating that fast intraprocedural analysis is + sufficient to detect most CF conflicts, whereas deeper interprocedural analysis might be essential to + uncover DF and OA conflicts. +

@@ -409,7 +411,7 @@

Authors