I would like to try to keep the GCC 4.2.x release branch on the time-driven release cycle for point releases that is part of the GCC development plan. I left an embarrassing gap in the GCC 4.1.x release cycle, and I plan to avoid that mistake for GCC 4.2.x.
Therefore, I plan to make the GCC 4.2.1 release on or about July 13th. As with the 4.2.0 release, I will be most concerned about P1 regressions in 4.2.x, not present in 4.1.x. At present, that looks to be: * PR 30252 miscompilation of sigc++-2.0 based code with -fstrict-aliasing * PR 31360 rtl loop invariant is broken This is a missed-optimization problem, fixed on the mainline -- although the audit trail suggests that there are unresolved problems on ARM, including bad code generation and CSiBE regressions. There are currently 128 P3-and-higher regressions from previous GCC releases that apply to the 4.2 branch. In order to actually make the release July 13th, I've put a note in my calendar to make 4.2.1 RC1 on July 1st. If there are 4.2.x regressions that you're interested in fixing, please do your best to fix them by that date. -- Mark Mitchell CodeSourcery [EMAIL PROTECTED] (650) 331-3385 x713