Re: [O] compilation issues of new export framework

2013-02-11 Thread Achim Gratz
Nicolas Goaziou writes: > I found that inlining it was an overkill. So the change is intentional. Thanks for the confirmation. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net

Re: [O] compilation issues of new export framework

2013-02-11 Thread Nicolas Goaziou
Achim Gratz writes: > Nicolas Goaziou gmail.com> writes: >> On the other hand, `org-element-type' and al. from org.el are called >> less often. So, it is not a problem if they are compiled as function >> calls. > > They are normally not compiled as function calls, only in single mode. > > Regard

Re: [O] compilation issues of new export framework

2013-02-10 Thread Achim Gratz
Nicolas Goaziou gmail.com> writes: > On the other hand, `org-element-type' and al. from org.el are called > less often. So, it is not a problem if they are compiled as function > calls. They are normally not compiled as function calls, only in single mode. Regarding commit 6b7101b91, did you int

Re: [O] compilation issues of new export framework

2013-02-10 Thread Nicolas Goaziou
Completing myself, Nicolas Goaziou writes: > Speed is the whole point, indeed. A quick profiling with and without > defsubst gives me: > > | defsubst | org-element-parse-buffer | 10 | 16.252699 |1.6252699 | > | defun| org-element-parse-buffer | 10 | 19.812426 | 1.9812425999 | > > It is a

Re: [O] compilation issues of new export framework

2013-02-10 Thread Nicolas Goaziou
Achim Gratz writes: > It comes from the two autoloads, or probably only the second one as the > first is later declare-function'ed anyway. If you declare these, then > the defsubst get sometimes compiled as function calls and sometimes as > inlined functions (the normal mode of compilation inlin

Re: [O] compilation issues of new export framework

2013-02-10 Thread Achim Gratz
Nicolas Goaziou writes: > Yes, I noticed this one too, but I don't know yet from where it could > come from. It comes from the two autoloads, or probably only the second one as the first is later declare-function'ed anyway. If you declare these, then the defsubst get sometimes compiled as functio

Re: [O] compilation issues of new export framework

2013-02-09 Thread Achim Gratz
Nicolas Goaziou writes: > Yes, I noticed this one too, but I don't know yet from where it could > come from. Hmm. If you don't know, then this is even more worrysome. Can't spend more time on this now, unfortunately. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk

Re: [O] compilation issues of new export framework

2013-02-09 Thread Nicolas Goaziou
Hello, Achim Gratz writes: > an oddity occurs since the new exporter moved into core (I don't think I > had seen this before, so maybe you can relate to what is different now): > > Compiling /lisp/org-mode/lisp/org.el... > Loading org-element... > Loading org-element... > Loading org-element...

Re: [O] compilation issues of new export framework

2013-02-09 Thread Achim Gratz
Hi Nicolas, an oddity occurs since the new exporter moved into core (I don't think I had seen this before, so maybe you can relate to what is different now): --8<---cut here---start->8--- Compiling /lisp/org-mode/lisp/org.el... Loading org-element... Loading or