Re: [Tinycc-devel] -fPIC anyone?

[Christian JULLIEN]

My only concern is that you should not use -fPIC by default in generated code as it introduces a performance penalty.
Too often I see libs that compile source only once code with -fPIC and generate both .so and .a out of them. It is perfectly legal and works well when .o goes in .a.
But stub is still there and I experimented performance penalties that range form 5 up to 20% in binaries using static libs compiled that way.

C.

----- message d'origine -----
De : "Jean-Claude Beaudoin" <address@hidden>
date mar. 27/09/2016 19:17 (GMT +02:00)
À : "tinycc-devel" <address@hidden>
Objet : [Tinycc-devel] -fPIC anyone?

Hello TCC devs,

I am starting an effort to implement -fPIC support for real in TCC.

The target is to have TCC generate full fledged shared libraries 

on ELF platforms.

Any objection?  Any advice?

I noticed also that "constructors" have been at the top of the TODO list

for ages now. If we are talking here of "__attribute__ ((constructor))" 

then I am definitely interested in knowing what is up with that too?

Cheers,

Jean-Claude Beaudoin

_______________________________________________
Tinycc-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/tinycc-devel