On Wed, Oct 19, 2011 at 07:11:02PM +0200, Tobias Burnus wrote: > I intent to commit this patch - created mostly by Janne - soon to > gcc-4_6-branch; it should solve a build issue. > > The patch was build and regtested on x86-64-linux and build and tested > on MinGW and Cygwin by Kai. > > It is a follow up to http://gcc.gnu.org/ml/fortran/2011-10/msg00132.html > / http://gcc.gnu.org/ml/gcc-cvs/2011-10/msg00734.html > > Please speak up immediately, if you have objects against the committal. > (Another option would be to revert previous patch, which solved a severe > performance regression on Windows - thus that patch plus this patch is > better.) > > Sorry for disrupting the 4.6.2 process a bit. >
I don't have an objection, just a question. Does this issue appear on trunk? Comment #10 in PR 50016 appears to suggest it does. In which case, I object to the initial commit into the 4.6-branch without testing the patch of trunk first. Rushing a patch into a branch to beat a release dead line is simply a poor choice. -- Steve