ixed this now with proper initialization.
After this correction the codes passes cleanly with valgrind and efence.
But this did not help, I still do get wrong code with "-fforce-addr",
the behaviour did not change at all.
Thanks,
Manfred
--
Ist Ihr Browser Vista-kompatib
> > Hi,
> >
> > I have a rather nasty optimization issue with gfortran (as of
> yesterday). As I think it could
> > be an optimization issue and not an gfortran frontend issue, I post it
> here,
> > the fortran list was not able to help so far.
> >
> > I narrowed my problem to one single fortran f
On Wed, Oct 03, 2007 at 12:24:27PM +0200, Manfred Schwarb wrote:
> I'm in a loss where to search for the real cause. Has anybody a hint
> how to proceed further?
Sounds like weird-but-somewhat-determinist behaviour you can get when
you do out-of-bounds access on the stack or this kind of problems.
On 10/3/07, Manfred Schwarb <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have a rather nasty optimization issue with gfortran (as of yesterday). As
> I think it could
> be an optimization issue and not an gfortran frontend issue, I post it here,
> the fortran list was not able to help so far.
>
> I narr
Hi,
I have a rather nasty optimization issue with gfortran (as of yesterday). As I
think it could
be an optimization issue and not an gfortran frontend issue, I post it here,
the fortran list was not able to help so far.
I narrowed my problem to one single fortran function. If I compile this
fu
