Re: Just what makes an architecture "C Friendly"?

Steve at fivetrees wrote:

.... snip ...

Unless I'm misunderstanding something, we're not talking about the
platform that the C compiler runs on. That's of no interest (to
me). We're talking about the target it compiles for.

As for "it is becoming an option more often to take the library
and file system and OS from development platform to the embedded
target with the minimal effort" - if you're talking about embedded
PCs, fine. Again that's of no interest to me, and I don't see how
it's relevant to this thread.

For many architectures there is little point in even trying to
implement an HLL. However it is still possible to use one to
organize the code, which will necessarily be in assembly. For this
purpose you can either simply use the HLL purely as descriptive
commentary, when its accuracy doesn't much matter, or try to make
that high level description compilable on something else. In that
latter case you want a language with the maximum security, such as
Pascal, since C won't catch many of your errors due largely to its
extremely loose typing. I call the last step of this technique
hand-compilation. It helps if the compiler is facile with the end
assembly language.

--
Some informative links:
news:news.announce.newusers
http://www.geocities.com/nnqweb/
http://www.catb.org/~esr/faqs/smart-questions.html
http://www.caliburn.nl/topposting.html
http://www.netmeister.org/news/learn2quote.html


.

Relevant Pages

  • Re: interesting use of NEXT SENTENCE vs. CONTINUE
    ... These days I don't do compiler maintenance, but I HAVE done in the past, so ... You had a chance to point out how adherence to the standard can improve ... >> compile it WITH MINOR MODIFICATIONS for a specific platform. ... > platform-specific extension to COBOL ...
    (comp.lang.cobol)
  • Re: interesting use of NEXT SENTENCE vs. CONTINUE
    ... I DID think any old compiler would be able to ... > compile it WITH MINOR MODIFICATIONS for a specific platform. ... > not going to go to the Standard to see what SHOULD work. ... If you write your COBOL code avoiding the things that are marked as ...
    (comp.lang.cobol)
  • Re: Standard Ada Preprocessor
    ... because Ada cannot deal with the portability issues. ... > you are interfacing directly to some special-purpose hardware. ... by their nature not compiler ... one platform you get 3 members back, and on another you get 5, ...
    (comp.lang.ada)
  • Re: C portability is a myth
    ... > solicitation for the availability of a compiler for a given platform. ... If the source is pure Standard C ... can be successfully ported to all implementations. ...
    (comp.lang.c)
  • Re: C portability is a myth
    ... > solicitation for the availability of a compiler for a given platform. ... People frequently talk about porting applications where no ... Yet further down you say the Java standard ports. ...
    (comp.lang.c)