Xref: utzoo comp.compilers:932 comp.lang.eiffel:945 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uunet!snorkelwacker!spdcc!esegue!compilers-sender From: graham@maths.su.oz.au (Graham Matthews) Newsgroups: comp.compilers,comp.lang.eiffel Subject: Eiffel and Efficiency Issues Message-ID: Date: 7 Jun 90 17:12:45 GMT Sender: compilers-sender@esegue.segue.boston.ma.us Reply-To: graham@maths.su.oz.au (Graham Matthews) Organization: Uni Computing Service, Uni of Sydney, Australia Lines: 15 Approved: compilers@esegue.segue.boston.ma.us In the Eiffel reference manual there are claims that Eiffel code (ie: C code generated by Eiffel) executes 20-25% (I think these figures are right?) slower than native C code. Can anyone tell me why this is? Is it just poor quality C code produced from the front end that is the cause of the problem? graham [My impression is that it is partly due to the time spend looking up methods and partly due to making things garbage collectable. Someone who is more familiar with the innards of Eiffel will, I hope, comment. -John] -- Send compilers articles to compilers@esegue.segue.boston.ma.us {spdcc | ima | lotus}!esegue. Meta-mail to compilers-request@esegue. Please send responses to the author of the message, not the poster.