Re: [xmlvm-users] memory bug found

[Gergely K. <ger...@ma...>]

Hi,

Actually it might make sense to add a set of -O compiler flags, so that it
is easier for the users to experiment with it, but the default settings
would generate "safe" code. What do you think?

Best Regards,
Gergely

2010/5/25 Arno Puder <ar...@pu...>

>
> I just commented out the faulty optimization in the repository. I don't
> think it makes sense to add a parameter for something that doesn't work.
>
> Arno
>
>
> On 5/25/10 8:22 AM, Panayotis Katsaloulis wrote:
> >
> > On 24 Μαϊ 2010, at 8:19 μ.μ., Joshua Melcon wrote:
> >
> >> Panayotis,
> >>
> >> This particular issue can occur in a variety of places.  In general
> >> they are very hard to detect unless you get lucky at runtime.  I
> >> strongly recommend commenting out:
> >>>> // new ExcessRetainsOptimization().Process(curRun.allCodePaths,
> curRun.beenTo,
> >>>> //            codeElement);
> >>
> >> in order to prevent any other nasty surprises.
> >>
> >> Regards,
> >>
> >> -- Joshua Melcon
> >>
> >
> >
> > Probably then this should be default for xmlvm?
> > Or what about a (hidden/advanced?)  parameter for xmlvm which will turn
> this on and off?
> >
> ------------------------------------------------------------------------------
> >
> > _______________________________________________
> > xmlvm-users mailing list
> > xml...@li...
> > https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>



-- 
Kis Gergely
MattaKis Consulting
Email: ger...@ma...
Web: http://www.mattakis.com
Phone: +36 70 408 1723
Fax: +36 27 998 622