Igor
I saw that method trailer were pushed into squeak. Do you plan to provide us a version for pharo? Or will we have to dig into squeak? Stef _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
I also noticed this. method trailer does not seem to be easy. There
are two phases apparently. Alexandre On 23 Dec 2009, at 13:33, Stéphane Ducasse wrote: > Igor > > I saw that method trailer were pushed into squeak. > Do you plan to provide us a version for pharo? > Or will we have to dig into squeak? > > Stef > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Stéphane Ducasse
I also contacted Nicolas C about his changes.
Alexandre On 23 Dec 2009, at 13:33, Stéphane Ducasse wrote: > Igor > > I saw that method trailer were pushed into squeak. > Do you plan to provide us a version for pharo? > Or will we have to dig into squeak? > > Stef > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Stéphane Ducasse
2009/12/23 Stéphane Ducasse <[hidden email]>:
> Igor > > I saw that method trailer were pushed into squeak. > Do you plan to provide us a version for pharo? > Or will we have to dig into squeak? > i made a changesets which should work ok on both forks. Lying over there http://bugs.squeak.org/view.php?id=7428 you can pick them up and see if they work for you.. Generally, after applying CompiledMethodTrailer-classes.3.cs trailers-utf8.1.cs trailers-phase1.1.cs trailers-phase2.1.cs trailers-phase3.2.cs pharo-phase4.1.cs check if you still having senders generate: #(0 0 0 0) and change them to just generate then , when you ready to convert, load : trailers-converting.1.cs and finally load: trailers-cleanup.1.cs after that, you could get DNUs, only if some obscure code still using a collection (usually #(0 0 0 0)) as trailer, instead of CompiledMethodTrailer instance. Alternatively, if you don't want to get an image into unusable state, before running a conversion, put halt in ArrayedCollection>>createMethod:header: to trap all of the places which still need to be fixed for using a new trailers. > Stef > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
there's also few more fixes, after applying initial ones.
Ask me to harvest them after you done installing trailers first. + Levente already made a changeset, which allows >32MB .source and .change files using new trailers. -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Alexandre Bergel
2009/12/23 Alexandre Bergel <[hidden email]>:
> I also noticed this. method trailer does not seem to be easy. There > are two phases apparently. > hehe... if you plan to adopt them using MC, it would require 4 stages. I split things on phases, to make sure that changes applied in correct order (because MC and changeSETs seems doesn't care too much about strictly following an order). > Alexandre > > > On 23 Dec 2009, at 13:33, Stéphane Ducasse wrote: > >> Igor >> >> I saw that method trailer were pushed into squeak. >> Do you plan to provide us a version for pharo? >> Or will we have to dig into squeak? >> >> Stef >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Igor Stasenko
2009/12/23 Igor Stasenko <[hidden email]>:
> 2009/12/23 Stéphane Ducasse <[hidden email]>: >> Igor >> >> I saw that method trailer were pushed into squeak. >> Do you plan to provide us a version for pharo? >> Or will we have to dig into squeak? >> > > i made a changesets which should work ok on both forks. > Lying over there > http://bugs.squeak.org/view.php?id=7428 > > you can pick them up and see if they work for you.. > > Generally, after applying > > CompiledMethodTrailer-classes.3.cs > trailers-utf8.1.cs > trailers-phase1.1.cs > trailers-phase2.1.cs > trailers-phase3.2.cs > pharo-phase4.1.cs > > check if you still having senders > > generate: #(0 0 0 0) > > and change them to just > > generate > > > then , when you ready to convert, load : > trailers-converting.1.cs > > and finally load: > > trailers-cleanup.1.cs > > after that, you could get DNUs, only if some obscure code still using > a collection (usually #(0 0 0 0)) as trailer, instead of > CompiledMethodTrailer instance. > > Alternatively, if you don't want to get an image into unusable state, > before running a conversion, put halt in ArrayedCollection>>createMethod:header: > using old format. Load some code from MC, play with traits etc.. and see if it will halt in this method. If not, then you are ready for conversion. > to trap all of the places which still need to be fixed for using a new trailers. > >> Stef >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
>> i made a changesets which should work ok on both forks.
>> Lying over there >> http://bugs.squeak.org/view.php?id=7428 >> >> you can pick them up and see if they work for you.. Ok I did not see this mail. I do not read squeak-dev. >> Generally, after applying >> >> CompiledMethodTrailer-classes.3.cs >> trailers-utf8.1.cs >> trailers-phase1.1.cs >> trailers-phase2.1.cs >> trailers-phase3.2.cs >> pharo-phase4.1.cs >> >> check if you still having senders >> >> generate: #(0 0 0 0) >> >> and change them to just >> >> generate >> >> >> then , when you ready to convert, load : >> trailers-converting.1.cs >> >> and finally load: >> >> trailers-cleanup.1.cs >> >> after that, you could get DNUs, only if some obscure code still using >> a collection (usually #(0 0 0 0)) as trailer, instead of >> CompiledMethodTrailer instance. >> >> Alternatively, if you don't want to get an image into unusable state, >> before running a conversion, put halt in ArrayedCollection>>createMethod:header: >> > Clarification: do not run conversion untill you fix every place which > using old format. > Load some code from MC, play with traits etc.. and see if it will halt > in this method. > If not, then you are ready for conversion. Ok can you help doing that? ie If we have problems be present :) Because I have no problem getting that in pharo but I do not want to do it blindly. So >> to trap all of the places which still need to be fixed for using a new trailers. >> >>> Stef >>> >>> _______________________________________________ _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
2009/12/23 Stéphane Ducasse <[hidden email]>:
>>> i made a changesets which should work ok on both forks. >>> Lying over there >>> http://bugs.squeak.org/view.php?id=7428 >>> >>> you can pick them up and see if they work for you.. > > > Ok I did not see this mail. > I do not read squeak-dev. > >>> Generally, after applying >>> >>> CompiledMethodTrailer-classes.3.cs >>> trailers-utf8.1.cs >>> trailers-phase1.1.cs >>> trailers-phase2.1.cs >>> trailers-phase3.2.cs >>> pharo-phase4.1.cs >>> >>> check if you still having senders >>> >>> generate: #(0 0 0 0) >>> >>> and change them to just >>> >>> generate >>> >>> >>> then , when you ready to convert, load : >>> trailers-converting.1.cs >>> >>> and finally load: >>> >>> trailers-cleanup.1.cs >>> >>> after that, you could get DNUs, only if some obscure code still using >>> a collection (usually #(0 0 0 0)) as trailer, instead of >>> CompiledMethodTrailer instance. >>> >>> Alternatively, if you don't want to get an image into unusable state, >>> before running a conversion, put halt in ArrayedCollection>>createMethod:header: >>> >> Clarification: do not run conversion untill you fix every place which >> using old format. >> Load some code from MC, play with traits etc.. and see if it will halt >> in this method. >> If not, then you are ready for conversion. > > Ok can you help doing that? ie If we have problems be present :) > Because I have no problem getting that in pharo but I do not want to do it > blindly. I will try loading .cs in the latest code image, once i get home today. And will tell you if there something more needs to be fixed. > So > >>> to trap all of the places which still need to be fixed for using a new trailers. >>> >>>> Stef >>>> >>>> _______________________________________________ > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Thanks a lot.
On Dec 23, 2009, at 2:25 PM, Igor Stasenko wrote: > 2009/12/23 Stéphane Ducasse <[hidden email]>: >>>> i made a changesets which should work ok on both forks. >>>> Lying over there >>>> http://bugs.squeak.org/view.php?id=7428 >>>> >>>> you can pick them up and see if they work for you.. >> >> >> Ok I did not see this mail. >> I do not read squeak-dev. >> >>>> Generally, after applying >>>> >>>> CompiledMethodTrailer-classes.3.cs >>>> trailers-utf8.1.cs >>>> trailers-phase1.1.cs >>>> trailers-phase2.1.cs >>>> trailers-phase3.2.cs >>>> pharo-phase4.1.cs >>>> >>>> check if you still having senders >>>> >>>> generate: #(0 0 0 0) >>>> >>>> and change them to just >>>> >>>> generate >>>> >>>> >>>> then , when you ready to convert, load : >>>> trailers-converting.1.cs >>>> >>>> and finally load: >>>> >>>> trailers-cleanup.1.cs >>>> >>>> after that, you could get DNUs, only if some obscure code still using >>>> a collection (usually #(0 0 0 0)) as trailer, instead of >>>> CompiledMethodTrailer instance. >>>> >>>> Alternatively, if you don't want to get an image into unusable state, >>>> before running a conversion, put halt in ArrayedCollection>>createMethod:header: >>>> >>> Clarification: do not run conversion untill you fix every place which >>> using old format. >>> Load some code from MC, play with traits etc.. and see if it will halt >>> in this method. >>> If not, then you are ready for conversion. >> >> Ok can you help doing that? ie If we have problems be present :) >> Because I have no problem getting that in pharo but I do not want to do it >> blindly. > > I will try loading .cs in the latest code image, once i get home today. > And will tell you if there something more needs to be fixed. > > >> So >> >>>> to trap all of the places which still need to be fixed for using a new trailers. >>>> >>>>> Stef >>>>> >>>>> _______________________________________________ >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Alexandre Bergel
Hi Alexandre,
I missed that probably... which changes ? Can you re-send at my gmail address? 'nicolas cellier aka nice' replaceAll: Character space with: $. ifrance is not that reliable... Nicolas 2009/12/23 Alexandre Bergel <[hidden email]>: > I also contacted Nicolas C about his changes. > > Alexandre > > > On 23 Dec 2009, at 13:33, Stéphane Ducasse wrote: > >> Igor >> >> I saw that method trailer were pushed into squeak. >> Do you plan to provide us a version for pharo? >> Or will we have to dig into squeak? >> >> Stef >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Free forum by Nabble | Edit this page |