On Apr 8, 7:23 am, vasile surducan <[email protected]> wrote:
> ARM (extended to DSP) and FPGA. For the FPGA  translation should be from Jal
> to Verilog or VHDL.

Greetings Vasile,

Thanks for giving the project some thought and for your interest and
questions.

FPGA -- Interesting and perhaps doable. Right now, the focus is on a
grammar and parser for the input. Output comes later. :-)  But just
curious, why not use FPGA with soft or hard support for C, for
instance microblaze or nios?

> For ARM, a translation from Jal to C, then a compilation under C (as I have
> understood is planned)
> imply a good knowledge of C even for the Jal user... so once C is well known
> why to bother with this
> weird combination?
>

Good question, I can only assume Wouter has a good reason, since he
was asking for something like this.  However, I think the person
providing support for a new chip may indeed need a good understanding
of C, but perhaps the end-user would not need C so much. Time will
tell.

> Maybe will be much easy to define an ARM family and try to generate the
> output code directly for that one?
> In that way, generic libraries conversion should be easier?

Maybe so, and no reason we can't try such an approach--  hopefully we
can share the same input grammar and parser, and provide multiple
different targets. Whichever one(s) becomes popular, we can choose
it.  The others may fall into disuse/neglect.

William

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/jallib?hl=en.

Reply via email to