On Sun, Jun 2, 2013 at 5:11 PM, Juan Jose Garcia-Ripoll <
juanjose.garciarip...@gmail.com> wrote:
> The problem: the compiler right now has two types of hardcoded dependencies
> 1 - Language features selected at build time (CLOS, threads, etc)
> 2 - Machine-dependent features (word sizes, bits, etc)
>
This is now started. A 'machine' object now stores information about the
compilation target. It is currently specialized to keep information about C
types and inline forms, but in the near future it should be fixed to
include also the compiler, linker and other features. It should also be
possible to recreate that structure at run-time with the help of autoconf.
Juanjo
--
Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain)
http://juanjose.garciaripoll.googlepages.com
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
_______________________________________________
Ecls-list mailing list
Ecls-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecls-list
