1. Introduction Purpose Objectives Content Learning Time
• This training course covers interoperability issues that exist between the Renesas SHC compiler and the KPIT GNUSH compiler.
Objectives
• Learn what interoperability means with regard to the Renesas SHC compiler and the KPIT GNUSH compiler.
• Learn how how interoperability is achieved between these compilers.
Content
• 6 pages
• 1 question
Learning Time
• 10 minutes
Welcome to the “Interoperability” course — one of a series of courses covering the GNU toolchain from KPIT Cummins Infosystems and microcontroller (MCU) support products from Renesas Technology. These development tools speed up the debugging of software for embedded systems. To get the most out of this material, you should understand the fundamentals of designing and developing embedded control systems.
This course explains what interoperability means with regard to the Renesas SHC compiler and the KPIT GNUSH compiler, and how it is achieved between these compilers.
Other courses in this series cover additional aspects of embedded system development and explain the use of different debugging tools.

2. What Interoperability Means
• A Renesas SHC-generated relocatable object file can be linked by the GNUSH linker
• A GNUSH-generated relocatable object file (compiled with the “-mrenesas” option) can be linked by the Renesas linker
Renesas SHC generated
relocatable object file
GNUSH generated relocatable object file
(Compiled with “-mrenesas” option)
Linked by
GNUSH linker
And
Linked by
Renesas linker
Not linked by
Renesas linker
Let’s start by defining the term “interoperability” as it is used in this course. Interoperability between the Renesas SHC compiler and the GNUSH compiler has two meanings. It means that a Renesas SHC-generated relocatable object file can be linked by the GNUSH linker. It also means that a GNUSH-generated relocatable object file can be linked by the Renesas linker if it’s compiled with the “-mrenesas” option. (If that file isn’t compiled with this option, it isn’t linked by the Renesas linker )
The example has three relocatable object files. The first, “RSH.o,” is produced by the Renesas SH C compiler. The other two files, “G1.o” and “G2.o,” are produced by the GNUSH compiler using the “-mrenesas” option. All three files are interoperable. They can be linked by the GNU linker and the Renesas linker.
Example of interoperability:
- Renesas SHC-generated relocatable object file: RSH.o.
- GNUSH-generated relocatable object files compiled with –mrenesas option: G1.o, G2.o.
When these files are interoperable, (G1.o + G2.o) + RSH.o can be linked by the GNU linker, as well as by the Renesas linker.

3. Application Binary Interface
An Application Binary Interface (ABI) is the low-level interface between:
an application program and the operating system
the application and its libraries
the component parts of the application
• ABIs cover details such as
- Calling convention, which controls how a function's arguments are passed and the return values are retrieved
- System call numbers and how an application should make system calls to the operating system
An Application Binary Interface (ABI) is the low-level interface between an application program and the operating system, the application program and its libraries, or the component parts of the application.
ABIs cover the calling convention, which controls how a function's arguments are passed and how its return values are retrieved. ABIs also cover the system call numbers and how an application should make system calls to the operating system.
The interoperability previously described is achieved because compiling with the “-mrenesas” option in GNUSH generates code that follows the Renesas SuperH calling conventions or Renesas ABI.
Interoperability is achieved because compiling with the “-mrenesas” option in GNUSH generates code that follows the Renesas SH calling conventions or Renesas ABI.

4. ABI (continued)
Using a compatible ABI, compiled object code can function on any system without any changes.
• The SH Application Binary Interface (ABI) for GCC is available at the following link:
• For Interoperability details, please visit:
Using a compatible ABI, compiled object code can function on any system without any changes. The SH ABI for the GNU Compiler Collection (GCC) is available on the KPIT GNU Tools website. This website also provides more information about interoperability.

5. Question
Is the following statement true or false? Click Done when you are finished.
“A GNUSH-generated relocatable object file (compiled using the ‘-mrenesas’ option) is interoperable and can be linked by the Renesas linker.”
True
False
Here’s a question for you.
Correct.
A GNUSH-generated relocatable object file compiled using the “-mrenesas” option is interoperable and can be linked by the Renesas linker.
Done

6. For more information, please visit our Web site:
Summary
• Meaning of interoperability
• How interoperability is achieved
This concludes the “Interoperability” course. You learned what interoperability is and how it is achieved between the Renesas SHC compiler and the GNUSH compiler with the “-mrenesas” option.
We now invite you to take the other courses in this GNU toolchain series, which cover additional aspects of embedded system development and how to use different debugging tools. Consider also taking other courses at this website on the HEW IDE, CPU architectures, specific Renesas microcontroller products, on-chip peripheral functions, and more.
Additionally, we encourage you to use the free VirtuaLab setups at this website to gain some hands-on experience with popular devices and tools without having to buy products and wait for delivery.
Thank you for your interest in Renesas microcontrollers and for taking advantage of the resources of the Renesas Interactive website. Please visit us often. Further, we urge you to bookmark the main Renesas website so you can obtain the latest product, application and support information whenever you need it.
For more information, please visit our Web site: