|Re: [eigen] limiting executable code size with debug info|
[ Thread Index | Date Index | More lists.tuxfamily.org/eigen Archives ]
On Monday 09 June 2008 16:57:37 Gael Guennebaud wrote: > but my project also has its own template mess so the overhead is not 100% > due to eigen2. It would be interesting to grab such statistics on kdelibs > for instance... Just FYI kdelibs is not using eigen and, as far as I can see, doesn't have a use for it. 57M code sounds huge... is it a really big project you're working on, or is it something really special that justifies having many template instantiations, or is it just that eigen and/or your other template stuff is generating far too much executable code? Cheers, Benoit > > Gael. > > On Mon, Jun 9, 2008 at 4:26 PM, Gael Guennebaud <gael.guennebaud@xxxxxxxxx> > > wrote: > > Hi, > > > > On Mon, Jun 9, 2008 at 9:06 AM, Benoît Jacob <jacob@xxxxxxxxxxxxxxx> > > wrote: <http://download.tuxfamily.org/eigen/benchmark-g1.s.gz> > > > >> So, does anybody have an idea what to do to make Eigen usable with -g2 ? > > > > yes of course, that's easy: > > > > let's rewrite eigen using QVariant to store the coefficients and virtual > > members ;) > > > > no, seriously I have no idea how to deal with that issue :( I know > > several template libraries which generate GB of .o in debug mode and I > > hate that... Maybe it'd be worth asking on GCC mailing list since the > > answer to this issue probably requires to know very well how GCC behaves > > internally. > > > > Gael.
Description: This is a digitally signed message part.
|Mail converted by MHonArc 2.6.19+||http://listengine.tuxfamily.org/|