Tim Prince wrote: > This doesn't seem to be a magically fully working gfortran, such as we > had fleetingly with the 20090227 snapshot of 4.4. I'd agree it's likely > an "upstream" problem, even if it shows up only on cygwin.
Hi Tim, can you give me a bit of context here? I don't know what sort of problems you're seeing or what "fully" working means here. And of course it's not going to reflect anything that happened after 4.3 branched. I noticed a few regressions in the testsuite, where the expected output doesn't show up - in fact no output showed up at all from the testcases. But when I tried to reproduce a few of them manually, they worked fine and generated the correct output, so I put it down to an artifact of the testsuite framework, maybe an interaction with tcl/expect and cygwin/win32 pipes, and figured I'd try and solve it before the next release. I don't know much about Fortran, so I can't necessarily solve problems in the front-end, but if the issues relate to generic compiler infrastructure such as stdio or exception handling I should be able to fix bugs. cheers, DaveK -- 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/