From Fedora Project Wiki
No edit summary
(Converted to https://teams.fedoraproject.org/project/changes-tracker/issue/2 and announced)
Line 81: Line 81:
The mingw32 toolchain in Fedora 32 uses the dwarf-2 exception model instead of SJLJ.
The mingw32 toolchain in Fedora 32 uses the dwarf-2 exception model instead of SJLJ.


[[Category:ChangeReadyForWrangler]]
[[Category:ChangeAnnounced]]
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->

Revision as of 20:54, 28 August 2019

Switch mingw32 toolchain to dwarf-2 exceptions

Summary

Switch the mingw32 toolchain to dwarf-2 exceptions, instead of SJLJ.

Owner

  • Name: Sandro Mani
  • Email: manisandro@gmail.com
  • Release notes owner:

Current status

  • Targeted release: Fedora 32
  • Last updated: 2019-08-28
  • Tracker bug: <will be assigned by the Wrangler>
  • Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

The two exception modesl supported by mingw32 targets are SJLJ (currently used in Fedora, and still default upstream), and the more recent dwarf-2. According to various sources [1][2][3], the key differences between the two are:

SJLJ (setjmp/longjmp):

  • not "zero-cost": even if an exception isn't thrown, it incurs a minor performance penalty (~15% in exception heavy code)
  • allows exceptions to traverse through e.g. windows callbacks

DWARF (DW2, dwarf-2)

  • no permanent runtime overhead
  • needs whole call stack to be dwarf-enabled, which means exceptions cannot be thrown over e.g. Windows system DLLs (i.e. throwing an exception in a system DLL callback and attempting to catch it won't work)
  • DW2 potentially generates bigger libraries. The overhead however is not big (< 10%) for typical applications.

The main reason for switching to dwarf-2 is that rust can only be compiled to a MinGW toolchain targeting dwarf exceptions on 32-bit [4], and rust usage is starting to appear in some packages (i.e. librsvg2). Switching to dwarf-2 on mingw32 would hence allow to keep the same consistent package offering between mingw32 and mingw64, whereas otherwise one would need to either freeze the mingw32 variants at older versions, or remove them altogether.


Benefit to Fedora

Continue being able to ship the same package set on mingw32 as well as mingw64.

Scope

  • Proposal owners:

GCC for mingw32 will be built with --disable-sjlj-exceptions --with-dwarf2 and all mingw-* packages rebuilt.

  • Other developers:

None

  • Release engineering: Rebuild in a side-tag
  • Policies and guidelines: No policies need to be changed

Upgrade/compatibility impact

No impact

Contingency Plan

  • Contingency mechanism: Revert to SJLJ
  • Contingency deadline: Before release
  • Blocks release? Yes
  • Blocks product? No

Documentation

None

Release Notes

The mingw32 toolchain in Fedora 32 uses the dwarf-2 exception model instead of SJLJ.