Hi Christoph, I'd see not much value in switching to debug builds for the snapshots. Currently the snapshots are public and are built with PGO. This makes it easy for users to test any provided revision. Debug builds are better suitable for the runtime development, but they require a debug runtime, can't use PGO and are in most case unusable for users.
IMO, if debug builds of snapshots are needed for something, they might be added, but release buids of snapshots should not be removed. It is more important to ensure release builds, for debug they're also suitable in 98% of cases as it always contains debug symbols. There are many other points that would speak against switching to debug builds only. For the developer needs, debug builds can always be done on demand. Regards Anatol On Thu, 2020-03-05 at 16:41 +0100, Christoph M. Becker wrote: > Hi all, > > the PHP for Windows team is considering to ship all PHP snapshot > builds[1] as debug builds in the future (earliest at the end of > March); > currently these are release builds. The reason for this change is > that > debug builds obviously have better debugging support (including but > not > limited to WER[2]), and also execute assertions and enable the basic > leak checking of Zend Memory Manager. > > Of course, the debug builds would be not as performant, and would be > larger in size, but that does not appear to be an issue for snapshot > builds. > > Thoughts? > > [1] <https://windows.php.net/snapshots/> > [2] > < > https://docs.microsoft.com/en-us/windows/win32/wer/windows-error-reporting > > > > -- > Christoph M. Becker > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
