Hi,

is there a publically available assembler and disassembler
for My 66000?

The reason I'm asking is that I'd like to run a code
size comparison on a "single basic block from hell" -
type piece of code, specifically on the test case for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80960 which was
autogenerated by a computer algebra system. It also turned
out to be a stress test for gcc :-)

This is, by the way, a perfectly valid use case, with its ~10000
assignment statements. Generating analytical expressions for
Jacobians with computer algebra systems is something that is often
done to avoid the pitfalls of numerical differentiation.

On Wednesday, September 14, 2022 at 1:40:38 AM UTC-5, Thomas Koenig wrote:
> Hi,
>
> is there a publically available assembler and disassembler
> for My 66000?
>
> The reason I'm asking is that I'd like to run a code
> size comparison on a "single basic block from hell" -
> type piece of code, specifically on the test case for
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80960 which was
> autogenerated by a computer algebra system. It also turned
> out to be a stress test for gcc :-)
>
> This is, by the way, a perfectly valid use case, with its ~10000
> assignment statements. Generating analytical expressions for
> Jacobians with computer algebra systems is something that is often
> done to avoid the pitfalls of numerical differentiation.
<
I defer to Brian.

The code for the assembler and disassembler (and functional simulator) is
available at github.com/bagel99/progtools in the my66000 directory.
That's the good news. The bad news is the code is written in my ESL
programming language. The compiler for ESL (front-end for LLVM) is in
github.com/bagel99/esl. The compiler will bootstrap using LLVM.

If one is running linux on x86-64, I could provide binaries for the
assembler and disassembler.

On 9/14/22 11:39, MitchAlsup wrote:
> On Wednesday, September 14, 2022 at 1:40:38 AM UTC-5, Thomas Koenig wrote:
>> Hi,
>>
>> is there a publically available assembler and disassembler
>> for My 66000?
>>
>> The reason I'm asking is that I'd like to run a code
>> size comparison on a "single basic block from hell" -
>> type piece of code, specifically on the test case for
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80960 which was
>> autogenerated by a computer algebra system. It also turned
>> out to be a stress test for gcc :-)
>>
>> This is, by the way, a perfectly valid use case, with its ~10000
>> assignment statements. Generating analytical expressions for
>> Jacobians with computer algebra systems is something that is often
>> done to avoid the pitfalls of numerical differentiation.
> <
> I defer to Brian.

Brian G. Lucas <bagel99@gmail.com> schrieb:
> The code for the assembler and disassembler (and functional simulator) is
> available at github.com/bagel99/progtools in the my66000 directory.
> That's the good news. The bad news is the code is written in my ESL
> programming language. The compiler for ESL (front-end for LLVM) is in
> github.com/bagel99/esl. The compiler will bootstrap using LLVM.

Can this be combined easily with the my66000 patch, or do I need
two different compilers for that? (You may want to keep when
answering that I hardly know the LLVM build process).

If it's just "copy over the directoy and compile", I will probably
be able to manage.

On 9/15/22 10:35, Thomas Koenig wrote:
> Brian G. Lucas <bagel99@gmail.com> schrieb:
>> The code for the assembler and disassembler (and functional simulator) is
>> available at github.com/bagel99/progtools in the my66000 directory.
>> That's the good news. The bad news is the code is written in my ESL
>> programming language. The compiler for ESL (front-end for LLVM) is in
>> github.com/bagel99/esl. The compiler will bootstrap using LLVM.
>
> Can this be combined easily with the my66000 patch, or do I need
> two different compilers for that? (You may want to keep when
> answering that I hardly know the LLVM build process).
>
> If it's just "copy over the directoy and compile", I will probably
> be able to manage.

I tested it and it should build with the my66000 patched LLVM. You
need to change the variable LLVM in the shell file src/llvm to
point to the directory that has the LLVM binaries.

On the other hand, one could just install the distributed LLVM for
your linux distribution.

brian