--- Ven 13/3/09, Dave Korn ha scritto:
> Da: Dave Korn
> Oggetto: Re: [ANNOUNCEMENT] Updated: experimental package: gcc4-4.3.2-2
> A:
> Data: Venerdì 13 marzo 2009, 07:41
> 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.
>
Hi Dave
I also noted such issue playing with the previous
4.3.2-1 and my own built cygfortran.dll, but I thought
was my fault.
It seems a problem of output redirection with dynamic
fortran library
if I had
./test_program
I see the output on the screen but
./test_program > test_output
leave test_output empty.
This did not happened with static linked fortran library.
test case:
------------------------------
program main
WRITE(*,*) 'SUCCESS'
end
------------------------------
> 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
>
Regards
Marco
--
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/
