Re: Ravenscar-compliant bounded buffer

[anon@anon.org (anon)]

WHERE IS YOU PROOF!!! If your going to call a person a liar then you 
should provide proof it or just say that your a TROLL and be done with 
it. It seams that people here love to argue but give no proof of what 
they say.  At least I give proof of what I have said in history posts.

Read NYU GNAT (before Adacore) internal messages regarding 
GNAT-RTS and GNU C compiling system. It is a direct internal C tree 
structure of the C code. That can be printed as a C program. Also there 
are a few web sites with doctoral thesis that states this as well as 
a few papers at ACM. And ACM group will verify the information before 
accepting thesis paper and this is where I learn of it. The paper include 
a program that will print internal C as a compilable C source code 
file.

Now since, the mid 1980's most compiler are FRONT_END compilers aka 
a language translator that converts the source language to the system's 
main language, normal for today that's C with the exception of TI which 
used Pascal.  Then the FRONT_END compiler calls a BACK_END compiler 
(for GNAT this is done by the compiler calling "gigi" (gnat-to-gcc)), 
which re-calls the gcc compiler for GNU system so that the internal C 
can be converted to a object module or assembly source file. 
{{ continue below }}

Now, any system build around GNAT will contain the C code that GNAT 
uses to connect to the operating system. And since GNAT is built 
with the GCC libraries the trig. and other math functions will be 
wriiten in C to interface with the FPU or to the FPU emulation 
package, which is also written in C. That make any system that is 
compiled with around GNAT not "Ada only Run-Time System". 

The XGC Ada which is based on GNAT and uses C for its Real Time 
application and TLD contains C close sources files from DEC's Ada
libraries, which denote that both do not have an "Ada only 
Run-Time System". 

>Then there is the Open Ravenscar Kernel ORK for GNAT, 
The only problem with that one is that it is 4 years and gcc lib 
are out dated.  The two I gave are current.


Stated this before too!

First, the MicroVax came out in, the mid 1980s and DEC created Ada 
in 1978. So, your MicroVax Ada version could of been the third 
released or third version sold to the general public by DEC. 


>For general (workstation, server) platforms of course Ada vendors 
>do the sensible thing and connect to the existing OS interfaces, in 
>most cases designed for C as the lowest common denominator.
>
>There have been full-Ada systems even outside the embedded domain. 
>Long ago, when Nokia (yes, the mobile phone company) was selling 
>computers they developed a 32-bit system called MPS10 to compete 
>with VAXes for data processing applications. The software, 
>including the OS and database system, was in Ada.


And I was talking about multi-platforms, which I stated. Which means 
that the system must operate on more than one processor and platforms 
class system. Like Nokia's Ada on a NCR or Univac system, which did 
not happen. 

Note: this information come from Intel web site during the release of 
the Itanium I processor. { continue from above }

Before GNU system the idea of multi-platform compilers basically did 
not happen, but since then the major software houses have adopted this 
concept. A quick reason is that once they create a new processor they 
do not have to re-write all of the compiler codes and libraries. Just 
create the C compiler and recompile the software system from there.

Plus, as I have stated before getting a new licenses or paying for a 
Software Patents to re-write the close source libraries is a high 
Dollar item. And most companies and users do not want to pay
that price or take the time and expense to re-write the code. So 
C is used.



In <46e28a6a$0$27847$39db0f71@news.song.fi>, Niklas Holsti <niklas.holsti@nospam.please> writes:
>anon wrote:
>
>> And the GNU/GPL GNAT Ada is just a frontend compiler to the GCC.  If 
>> you look at the source code "Back_end.adb" you will see a link to a C 
>> coded procedure called gigi (gnat-to-gcc) which calls the C "Run-Time" 
>> compiler. The C "Run-Time" compiler then converts the GNAT C 
>> generated code to the object modules.
>
>Saying that GNAT generates C code is nonsense, as you have been 
>answered earlier on this newsgroup. The GU Compiler Collection has 
>a common internal program representation that interfaces the front 
>ends to the back end, but this representation is not C.
>
>> For GNAT and most other Ada systems there is no Ada only "Run-Time 
>> System".
>
>That does not agree with my experience. Two of the three Ada 
>systems for embedded platforms that I have used have had their own 
>Ada RTS: TLD Ada and XGC Ada. XGC Ada is based on the GNAT compiler 
>but has its own kernel and libraries (mostly written in Ada, too, 
>as far as I remember).
>
>The third compiler was DEC Ada. I used it for applications on a 
>microVAX under VMS but as I remember it could also create programs 
>to run on a simpler real-time kernel called VAXELN. I think VAXELN 
>was not written in Ada and could also be used from other languages. 
>And why not.
>
>Then there is the Open Ravenscar Kernel ORK for GNAT, 
>http://polaris.dit.upm.es/~ork/, also written in Ada.
>
>For general (workstation, server) platforms of course Ada vendors 
>do the sensible thing and connect to the existing OS interfaces, in 
>most cases designed for C as the lowest common denominator.
>
>There have been full-Ada systems even outside the embedded domain. 
>Long ago, when Nokia (yes, the mobile phone company) was selling 
>computers they developed a 32-bit system called MPS10 to compete 
>with VAXes for data processing applications. The software, 
>including the OS and database system, was in Ada.
>
>-- 
>Niklas Holsti
>Tidorum Ltd
>niklas holsti tidorum fi
>       .      @       .