Speculative execution exception recovery using write-back suppression

Roger A. Bringmann, Scott A. Mahlke, Richard E. Hank, John C. Gyllenhaal, Wen-Mei W Hwu

Research output: Chapter in Book/Report/Conference proceedingConference contribution


Compiler-controlled speculative execution has been shown to be effective in increasing the available instruction level parallelism (ILP) found in non-numeric programs. An important problem associated with compiler-controlled speculative execution is to accurately report and handle exceptions caused by speculatively executed instructions. Previous solutions to this problem incur either excessive hardware overhead or significant register pressure. This paper introduces a new architectural scheme referred to as write-back suppression. This scheme systematically suppresses register file updates for subsequent speculative instructions after an exception condition is detected for a speculatively executed instruction. We show that with a modest amount of hardware, write-back suppression supports accurate reporting and handling of exceptions for compiler-controlled speculative execution with minimal additional register pressure. Experiments based on a prototype compiler implementation and hardware simulation indicate that ensuring accurate handling of exceptions with write-back suppression incurs little run-time performance overhead.

Original languageEnglish (US)
Title of host publicationProceedings of the Annual International Symposium on Microarchitecture
Editors Anon
PublisherPubl by IEEE
Number of pages10
ISBN (Print)0818652802
StatePublished - 1994
EventProceedings of the 26th Annual International Symposium on Microarchitecture - Austin, TX, USA
Duration: Dec 1 1993Dec 3 1993


OtherProceedings of the 26th Annual International Symposium on Microarchitecture
CityAustin, TX, USA

ASJC Scopus subject areas

  • Hardware and Architecture
  • Software


Dive into the research topics of 'Speculative execution exception recovery using write-back suppression'. Together they form a unique fingerprint.

Cite this