Untitled

Baker, Jason D.; Cunei, Antonio; Kalibera, Tomas; Pizlo, Filip; Vítek, Jan

doi:10.1002/cpe.v21:12

Cited by 15 publications

(1 citation statement)

References 123 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Often garbage collectors avoid to explicitly walk the stack either by allocating all the roots in an explicit pointer stack [Siebert 2001], or by keeping an explicit lists across stack frames [Henderson 2002]. Other approaches, as the lazy pointer stacks by Baker et al [2009], identify all the stack allocated pointers by walking the stack at a GC safe point, and require reliable unwind tables.…”

Section: Related Workmentioning

confidence: 99%

Reliable and fast DWARF-based stack unwinding

Bastian¹,

Kell

Nardelli

2019

Proc. ACM Program. Lang.

View full text Add to dashboard Cite

Debug information, usually encoded in the DWARF format, is a hidden and obscure component of our computing infrastructure. Debug information is obviously used by debuggers, but it also plays a key role in program analysis tools, and, most surprisingly, it can be relied upon by the runtime of high-level programming languages. For instance the C++ runtime leverages DWARF stack unwind tables to implement exceptions! Alas, generating debug information adds significant burden to compiler implementations, and the debug information itself can be pervaded by subtle bugs, making the whole infrastructure unreliable. Additionally, interpreting the debug tables is a time-consuming task and, for some applications as sampling profilers, it turns out to be a performance bottleneck. In this paper we focus on the DWARF .eh_frame table, that enables stack unwinding in absence of framepointers. We will describe two techniques to perform validation and synthesis of the DWARF stack unwinding tables, and their implementation for the x86_64 architecture. The validation tool has proven effective for compiler and inline assembly testing, while the synthesis tool can generate DWARF unwind tables for arbitrary binaries lacking debug information. Additionally, we report on a technique to precompile unwind tables into native x86_64 code, which we have implemented and integrated into libunwind, resulting in 11x-25x DWARF-based unwind speedups. CCS Concepts: • Software and its engineering → Compilers; Software testing and debugging.

show abstract

Section: Related Workmentioning

confidence: 99%

Reliable and fast DWARF-based stack unwinding

Bastian¹,

Kell

Nardelli

2019

Proc. ACM Program. Lang.

View full text Add to dashboard Cite

show abstract

Evaluation of a Java Ahead-of-Time Compiler for Embedded Systems

Jung

Moon

Bae

2011

The Computer Journal

View full text Add to dashboard Cite

Java embedded systems often include Java middleware classes installed on the client device. For higher performance, they can be compiled into machine code before runtime using an ahead-oftime compiler (AOTC). There are many approaches to AOTC, yet a bytecode-to-C (b-to-C) AOTC which translates the bytecode into the C code and then compiles it using an existing optimizing compiler such as gcc would be the most straightforward one. This paper explores a few important design and optimization issues of a b-to-C AOTC, including the compilation form for the translated C code, the call interfaces among translated and interpreted Java methods, and Java-specific optimizations by the AOTC that can complement the gcc optimizations. We evaluate these issues with our b-to-C AOTC implemented on the MIPS platform for the Sun's CDC VM to understand their performance impact.

show abstract

Improving Timeliness and Visibility in Publishing Software Engineering Research

Dwyer¹

2017

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

Ç W E believe that the role of TSE is to serve and connect the growing international community of software engineering researchers and practitioners. The TSE editorial board has continued to uphold the high standard of quality that has been a hallmark of the journal since its inception. In addition, we have worked in a number of areas to provide more timely and more visible content for the community.Timeliness. In 2015 we instituted certain paper review practices and this has led to a reduction in the time it takes to reach a decision and to publish accepted manuscripts.Specifically, the average number of days from submission of a manuscript to TSE until a final decision is sent to the authors has been reduced from 144 in 2014 to 98 in 2016. This represents a more than 6 week reduction in review time and brings the average time in review for TSE to just over 3 months. Review time varies of course, depending on whether a paper is rejected on first review or goes through major revisions, so the average is only part of the story.Our new practices have also reduced the time it takes from original submission to when the electronic version of an accepted manuscript is published. In 2014 this took, on average, 365 days, but we were able to reduce that by over 16 weeks to 250 days in 2016. The upshot is that, on average, accepted TSE manuscripts now appear online in just over 8 months.These improvements have been a team effort and we would like to thank John Grundy and Christine Shaughnessy, who worked with the editorial board to develop and implement strategies for improving the timeliness of TSE reviewing. The editorial board, and the community of reviewers, also deserves thanks for their part in implementing the new review practices.We believe that these efforts have maintained review quality. Evidence of this can be found in the fact that the TSE acceptance rate is the same, at 21.6%, in 2016 as it was in 2014, and the number of papers for which authors have questioned the review outcomes has decreased. We received feedback about review outcomes for 5 papers in 2014, 0.9% of submissions, and for 4 papers in 2016, 0.6% of submissions.Our goal is to continue to perform the highest-quality review, but to make sure that we expedite the review process so that results get out to the community as soon as possible. We believe that this is especially important as we continue to develop the journal-first publication model at TSE (more on that below).Visibility. The TSE editorial board has taken a leadership role in helping to establish a journal-first publication model for the software engineering research community.

show abstract

Untitled

Cited by 15 publications

References 123 publications

Reliable and fast DWARF-based stack unwinding

Reliable and fast DWARF-based stack unwinding

Evaluation of a Java Ahead-of-Time Compiler for Embedded Systems

Improving Timeliness and Visibility in Publishing Software Engineering Research

Contact Info

Product

Resources

About