Brian Dessent wrote:
I just want to remind everyone that using --enable-fully-dynamic-string will incur a somewhat significant performance hit, and it's the reason this hasn't been set as the default for Cygwin. In the PR there is a patch that is reported to fix the problem without the full performance hit, so that would be preferable to use rather than the 20-ton hammer.
The fuzzy semi-conclusion of the bug report scared me off - figured it'd be a safer choice to go with 'known to work but slower' that wouldn't add a draft patch to the diffs while they finish sorting it out in gcc land.
Either way, I'd just like to see this bug fixed. :) 'slow' or 'draft', anything is better than the current: 'crash'. I'm not sure who the current gcc maintainer of Cygwin is - I think Gerrit? If it's a time issue for him, I could build the packages and fix the sh/diff this weekend given a call on which path to take - draft patch or --enable-fully-dynamic-string. I just don't want it to fall through the cracks again.
-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
