Is the XMOS instruction set liable to change?

Technical questions regarding the xTIMEcomposer, xSOFTip Explorer and Programming with XMOS.
User avatar
dave
Member++
Posts: 31
Joined: Thu Dec 10, 2009 10:11 pm

Re: Is the XMOS instruction set liable to change?

Postby dave » Tue Dec 29, 2009 11:35 pm

As far as the pipeline goes. There is never more than one instruction from any specific thread in the pipeline. One stage in the pipeline is used for memory access. For branch instructions, this stage is used to fetch the instruction(s) at the branch target if the branch is taken. There is no need for a branch target cache. The timing is the same whether or not the branch is taken.
Heater
Respected Member
Posts: 296
Joined: Thu Dec 10, 2009 10:33 pm

Postby Heater » Tue Dec 29, 2009 11:52 pm

Thank you David.

The lesson is clear, as a veteran cycle counter I have to foster the habit of using the available timing facilities, clocked ports, serializers etc instead. Oh, and be careful with divides.

Good to hear that branches have the same execution time whichever way they go, I'm sure I will find myself counting cycles sometimes.

Speaking of which I understand that soon there will be a tool to perform timing analysis. I'm intrigued by this idea. I have only ever worked with one compiler that could report the exact execution time of your programs. That was Lucol from Lucas Aerospace.
User avatar
leon_heller
XCore Expert
Posts: 546
Joined: Thu Dec 10, 2009 10:41 pm
Location: St. Leonards-on-Sea, E. Sussex, UK.

Postby leon_heller » Wed Dec 30, 2009 12:51 am

There already is a tool for that, it's xta.exe. Download the tutorial (xtatut.pdf).

Leon
yzoer
XCore Addict
Posts: 133
Joined: Tue Dec 15, 2009 10:23 pm

Postby yzoer » Mon Jan 04, 2010 11:38 pm

Heater wrote:Thank you David.

The lesson is clear, as a veteran cycle counter I have to foster the habit of using the available timing facilities, clocked ports, serializers etc instead. Oh, and be careful with divides.

Good to hear that branches have the same execution time whichever way they go, I'm sure I will find myself counting cycles sometimes.

Speaking of which I understand that soon there will be a tool to perform timing analysis. I'm intrigued by this idea. I have only ever worked with one compiler that could report the exact execution time of your programs. That was Lucol from Lucas Aerospace.
I went through similar growing pains trying to get the VGA and NTSC timing up and running. Apart from non-timing critical performance optimizations, relying on clocked-ports is really the way to go! Absolutely brilliant!

-Yvo

Who is online

Users browsing this forum: No registered users and 1 guest