Re: [Pharo-project] 64 bit images (was Re: [squeak-dev] The Trunk: Collections-dtl.268.mcz)
Hi, I made a new version of the system-tracer (in attachment). It works fine with the latest pharo version. For wordSize, we decide to create a instance variable in SmalltalkImage, which is initialized at startup. The method initialPC is: --- initialPC "Answer the program counter for the receiver's first bytecode." ^ (self numLiterals + 1) * SmalltalkImage current wordSize + 1 --- The fix will be integrated in Pharo soon. It is also in attachment. Cheers On Jan 3, 2010, at 06:46 , John M McIntosh wrote:
Ok, well I was hoping that Laval Jannik would review the changes/solution in http://bugs.squeak.org/view.php?id=7430 then update his original System-Tracing.2forPharo3.cs Then test to confirm we can build a 64bit image from the current Pharo image
On 2010-01-02, at 6:46 PM, David T. Lewis wrote:
John, one additional note.
The SystemTracer changesets currently in circulation have an obsolete implementation of SystemDictionary>>wordSize.The original 64-bit Squeak used vmParameterAt: 27 for the VM to answer its word size, but this was later changed to vmParameter at: 40. This is the reason that the original "dist3" 64-bit image does not work on current VMs.
You will want to revert #wordSize back to a current version so that it uses vmParameter at: 40.
This issue will go away when we implement the cached #wordSize fixes discussed separately (http://bugs.squeak.org/view.php?id=7430), but I wanted to mention it because I spotted the obsolete method in the System-Tracing2forPharo.cs change set.
-- =========================================================================== John M. McIntosh <johnmci@smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================
--- Jannik Laval ---
Jannik did you check the changeset in the mantis bug report? Stef On Jan 4, 2010, at 10:53 AM, Laval Jannik wrote:
Hi,
I made a new version of the system-tracer (in attachment). It works fine with the latest pharo version.
For wordSize, we decide to create a instance variable in SmalltalkImage, which is initialized at startup. The method initialPC is:
--- initialPC "Answer the program counter for the receiver's first bytecode."
^ (self numLiterals + 1) * SmalltalkImage current wordSize + 1 ---
The fix will be integrated in Pharo soon. It is also in attachment.
<addWordSizeInSystemDictionary.1.cs><System-Tracing-forPharo.cs>
Cheers
On Jan 3, 2010, at 06:46 , John M McIntosh wrote:
Ok, well I was hoping that Laval Jannik would review the changes/solution in http://bugs.squeak.org/view.php?id=7430 then update his original System-Tracing.2forPharo3.cs Then test to confirm we can build a 64bit image from the current Pharo image
On 2010-01-02, at 6:46 PM, David T. Lewis wrote:
John, one additional note.
The SystemTracer changesets currently in circulation have an obsolete implementation of SystemDictionary>>wordSize.The original 64-bit Squeak used vmParameterAt: 27 for the VM to answer its word size, but this was later changed to vmParameter at: 40. This is the reason that the original "dist3" 64-bit image does not work on current VMs.
You will want to revert #wordSize back to a current version so that it uses vmParameter at: 40.
This issue will go away when we implement the cached #wordSize fixes discussed separately (http://bugs.squeak.org/view.php?id=7430), but I wanted to mention it because I spotted the obsolete method in the System-Tracing2forPharo.cs change set.
-- =========================================================================== John M. McIntosh <johnmci@smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================
--- Jannik Laval ---
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Yes, but the changeset build the fix in SystemDictionary, In a previous discussion, we decide to create an instance variable in SmalltalkImage and to put methods in SmalltalkImage too. Cheers, Jannik On Jan 4, 2010, at 13:35 , Stéphane Ducasse wrote:
Jannik
did you check the changeset in the mantis bug report?
Stef On Jan 4, 2010, at 10:53 AM, Laval Jannik wrote:
Hi,
I made a new version of the system-tracer (in attachment). It works fine with the latest pharo version.
For wordSize, we decide to create a instance variable in SmalltalkImage, which is initialized at startup. The method initialPC is:
--- initialPC "Answer the program counter for the receiver's first bytecode."
^ (self numLiterals + 1) * SmalltalkImage current wordSize + 1 ---
The fix will be integrated in Pharo soon. It is also in attachment.
<addWordSizeInSystemDictionary.1.cs><System-Tracing-forPharo.cs>
Cheers
On Jan 3, 2010, at 06:46 , John M McIntosh wrote:
Ok, well I was hoping that Laval Jannik would review the changes/solution in http://bugs.squeak.org/view.php?id=7430 then update his original System-Tracing.2forPharo3.cs Then test to confirm we can build a 64bit image from the current Pharo image
On 2010-01-02, at 6:46 PM, David T. Lewis wrote:
John, one additional note.
The SystemTracer changesets currently in circulation have an obsolete implementation of SystemDictionary>>wordSize.The original 64-bit Squeak used vmParameterAt: 27 for the VM to answer its word size, but this was later changed to vmParameter at: 40. This is the reason that the original "dist3" 64-bit image does not work on current VMs.
You will want to revert #wordSize back to a current version so that it uses vmParameter at: 40.
This issue will go away when we implement the cached #wordSize fixes discussed separately (http://bugs.squeak.org/view.php?id=7430), but I wanted to mention it because I spotted the obsolete method in the System-Tracing2forPharo.cs change set.
-- =========================================================================== John M. McIntosh <johnmci@smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================
--- Jannik Laval ---
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
excellent On Jan 4, 2010, at 1:44 PM, Laval Jannik wrote:
Yes, but the changeset build the fix in SystemDictionary, In a previous discussion, we decide to create an instance variable in SmalltalkImage and to put methods in SmalltalkImage too.
Cheers, Jannik
On Jan 4, 2010, at 13:35 , Stéphane Ducasse wrote:
Jannik
did you check the changeset in the mantis bug report?
Stef On Jan 4, 2010, at 10:53 AM, Laval Jannik wrote:
Hi,
I made a new version of the system-tracer (in attachment). It works fine with the latest pharo version.
For wordSize, we decide to create a instance variable in SmalltalkImage, which is initialized at startup. The method initialPC is:
--- initialPC "Answer the program counter for the receiver's first bytecode."
^ (self numLiterals + 1) * SmalltalkImage current wordSize + 1 ---
The fix will be integrated in Pharo soon. It is also in attachment.
<addWordSizeInSystemDictionary.1.cs><System-Tracing-forPharo.cs>
Cheers
On Jan 3, 2010, at 06:46 , John M McIntosh wrote:
Ok, well I was hoping that Laval Jannik would review the changes/solution in http://bugs.squeak.org/view.php?id=7430 then update his original System-Tracing.2forPharo3.cs Then test to confirm we can build a 64bit image from the current Pharo image
On 2010-01-02, at 6:46 PM, David T. Lewis wrote:
John, one additional note.
The SystemTracer changesets currently in circulation have an obsolete implementation of SystemDictionary>>wordSize.The original 64-bit Squeak used vmParameterAt: 27 for the VM to answer its word size, but this was later changed to vmParameter at: 40. This is the reason that the original "dist3" 64-bit image does not work on current VMs.
You will want to revert #wordSize back to a current version so that it uses vmParameter at: 40.
This issue will go away when we implement the cached #wordSize fixes discussed separately (http://bugs.squeak.org/view.php?id=7430), but I wanted to mention it because I spotted the obsolete method in the System-Tracing2forPharo.cs change set.
-- =========================================================================== John M. McIntosh <johnmci@smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================
--- Jannik Laval ---
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
participants (2)
-
Laval Jannik -
Stéphane Ducasse