[Pharo-dev] Compiler Explorer (for the Compiler guys) #offtopic

Esteban A. Maringolo emaringolo at gmail.com
Wed Oct 18 09:03:03 EDT 2017


Dolphin's debugger was what came to my mind, it had the "dissasembly" way
of debugging VM bytecode.
It doesn't provide was native code ASM, and as I understand GTInspector
neither.

Regards!

Esteban A. Maringolo

2017-10-18 6:55 GMT-03:00 Dimitris Chloupis <kilon.alios at gmail.com>:

> Yeap GTInspector was the first thing that came to my mind , great tool :)
>
> On Wed, Oct 18, 2017 at 9:37 AM Tudor Girba <tudor at tudorgirba.com> wrote:
>
>> Hi,
>>
>> This is already available since some time in the GTInspector. You can
>> just inspect a compiled method. You will get both the bytecode and the AST
>> (with source tracking, too). In fact, this was one of the original reasons
>> why GTInspector exists: I wanted to figure out how the AST is structured so
>> that I can write queries against it :).
>>
>>
>> Cheers,
>> Doru
>>
>>
>> On Oct 17, 2017, at 10:03 PM, Esteban A. Maringolo <emaringolo at gmail.com>
>> wrote:
>>
>> I'm sure we could do this with ease, because we already can see the
>> bytecodes.
>>
>> https://godbolt.org/
>>
>> Regards!
>>
>> Esteban A. Maringolo
>>
>>
>> --
>> www.tudorgirba.com
>> www.feenk.com
>>
>> "The coherence of a trip is given by the clearness of the goal."
>>
>>
>>
>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20171018/81937f8e/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dissasembly.png
Type: image/png
Size: 97446 bytes
Desc: not available
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20171018/81937f8e/attachment.png>


More information about the Pharo-dev mailing list