[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: [PATCH] Replace KisVector2D by Eigen
From:       jacob () math ! jussieu ! fr
Date:       2008-08-22 21:53:59
Message-ID: 20080822235359.r6p60xl28084wcss () mail ! math ! jussieu ! fr
[Download RAW message or body]

Quoting Matthew Woehlke <mw_triad@users.sourceforge.net>:

> jacob@math.jussieu.fr wrote:
>> Quoting Matthew Woehlke <mw_triad@users.sourceforge.net>:
>>> Hmm, I seem to be using debugfull, is *that* why KDE4 seems to be such a
>>> pig? ;-)
>>
>> Hm, Eigen2 is not currently used in KDE outside of KOffice so at least
>> it can't be the culprit here ;)
>
> You think compiling with no optimization wouldn't make an overall
> difference in performance? ;-) I guess in theory it shouldn't be huge in
> used RAM though. Ah, well. Anyway, I'm not actively running gdb on
> anything, probably I should rebuild w/o debugfull regardless.

Ah, I misunderstood your question as "is Eigen2 the reason why KDE4  
seems to be such a pig".

Compiling with -O2 doesn't prevent you from running gdb, -O2 is  
perfectly compatible with -g (generate debug info). There is one case  
when it can interfere with debugging: -O2 will inline many trivial  
functions, so you can't see them in gdb. I don't think this can be  
much of a problem in KDE or KOffice. But e.g. when I debug Eigen  
itself (that is, its unit-tests) I compile without optimization in  
order to see the trivial functions.

Cheers,
Benoit

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]