Renesas HEW

For the H8 target, I've found that the KPIT sources are often ahead of the FSF sources. KPIT appears to have been pretty active in improving the H8 support in gcc, and a lot of fixes/improvements show up in their packages before they make it into the "official" tree. It doesn't sound like they're as active with the Mistubishi targets.

--
Grant Edwards                   grante             Yow!  I want DUSTIN
                                  at               HOFFMAN!! ... I want
                               visi.com            LIBRACE!! YOW!!

Hi,

As you rightly said, we take latest, stable source snapshot from FSF, build the tool chain and package the installer so as to run on Windows as well as Linux. We release KPIT GNU tool chains every four months i.e. 3 release a year. All KPIT GNU tool chains get automatically integrated into Renesas HEW IDE.

official ones.

We will be posting modified patches after incorporating your comments into it. We will also be posting couple of problems we found in existing patches.

We mention the source versions, known problems and new enhancement or information about bug fixes in the release notes of KPIT GNU tool chain.

Though we take latest stable snapshot or released version of source, we are not completely dependent on regression results of that source. We have our own set of test cases written to test the compiler, libraries. We also have our own test Suite to test DWARF2 output generated i.e. debugging capacity of compiler. Moreover, we also test all samples on actual Renesas hardware kits in release as well as debug mode, with and without optimization enabled. We publish whatever problems we found in testing and could not be fixed in specified Time, in Release notes. If we have any workaround for same, we write that too.

You may find lot of useful documents on

like compiler, Assembler manuals, migration guides for users who want to migrate from proprietary compiler to GNU compiler. More importantly, you can get ABI descriptions for all GNU tool chains targeted for Renesas SH, H8/300 and R8C, M16C, M32C families of processors. Simply, click on "Documentation" -> "User Manuals" and choose the document you want to read.

Regards, Anil Paranjpe

Hi,

As you rightly said, we take latest, stable source snapshot from FSF, build the tool chain and package the installer so as to run on Windows as well as Linux. We release KPIT GNU tool chains every four months i.e. 3 release a year. All KPIT GNU tool chains get automatically integrated into Renesas HEW IDE.

official ones.

We will be posting modified patches after incorporating your comments into it. We will also be posting couple of problems we found in existing patches.

We mention the source versions, known problems and new enhancement or information about bug fixes in the release notes of KPIT GNU tool chain.

Though we take latest stable snapshot or released version of source, we are not completely dependent on regression results of that source. We have our own set of test cases written to test the compiler, libraries. We also have our own test Suite to test DWARF2 output generated i.e. debugging capacity of compiler. Moreover, we also test all samples on actual Renesas hardware kits in release as well as debug mode, with and without optimization enabled. We publish whatever problems we found in testing and could not be fixed in specified Time, in Release notes. If we have any workaround for same, we write that too.

You may find lot of useful documents on

like compiler, Assembler manuals, migration guides for users who want to migrate from proprietary compiler to GNU compiler. More importantly, you can get ABI descriptions for all GNU tool chains targeted for Renesas SH, H8/300 and R8C, M16C, M32C families of processors. Simply, click on "Documentation" -> "User Manuals" and choose the document you want to read.

Regards, Anil Paranjpe

That is a waste of time incorporating into HEW, having spent some time with it now, it is only useful for throw away apps that do not require maintenence for more than 2 months. HEW seems targetted at PC applications developers toying with embedded, too many files get incorporated that are not needed, the linker script gets embedded into HEW specific files. Changing toolchain is not possible without recreating a 'workspace', there is special commands to change toolchain version!

Persoanlly if it had a simpler version that allowed easier debug/simulator only without loads of unnecessary wizards, it might be worthwhile.

The fact that the look and feel is almost identical to FDT (for flashing devices) is too much of a recipe for trouble. The interface methods on both apps are too clunky and full of wizards and lots of mouse clicks. Nothing is logically laid out, all debug functions under one LONG menu.

Only one workspace file of ANY name in one directory and inability to easily duplicate one workspace to become another workspace (or template) using same or different toolchain is painful.

Overall it is too much work for what it is trying to achieve. Makes documentation and maintenance of any project that has to be maintained for a year or more nearly imposible. Current projects may well have to be supported for 10 years or more.

....

I found other sources more useful.

Hmm ABI specs came originally from elsewhere, the manuals in my view are sparse (Renesas ones as well).

--
Paul Carpenter          | paul@pcserviceselectronics.co.uk
    PC Services
              GNU H8 & mailing list info
             For those web sites you hate

Hi Paul,

Kindly let us know the document sources you are referring too. This will help us to improve the documentation on kpitgnutools website.

The advantage of this is programmer can refer to ABI of all Renesas target GNU compilers at one place.

Regards, Anil Paranjpe