[Bug lto/41681] Feature request half way option between dynamic and static linking.

2009-10-13 Thread rguenth at gcc dot gnu dot org
--- Comment #4 from rguenth at gcc dot gnu dot org 2009-10-13 09:46 --- So your half-way would be only useful for static analysis, but not for any optimization decision. Consider a function currently being void doIt() {} in the shared library. Now, if GCC sees the body it can deduce

[Bug lto/41681] Feature request half way option between dynamic and static linking.

2009-10-13 Thread oiaohm at gmail dot com
--- Comment #3 from oiaohm at gmail dot com 2009-10-13 08:03 --- Currently for libstdc++ it must be either dynamic or static. This separation causes some problems. There need to be two halfway points. The static libs the dynamic both be there. Type one halfway is for secuirty reasons

[Bug lto/41681] Feature request half way option between dynamic and static linking.

2009-10-12 Thread pinskia at gcc dot gnu dot org
--- Comment #2 from pinskia at gcc dot gnu dot org 2009-10-12 20:06 --- I don't understand what you are asking for either. Static libraries and dynamic libraries are usually two separate files (except under AIX) so it would be hard to decide to do one or another. Even if we figure that

[Bug lto/41681] Feature request half way option between dynamic and static linking.

2009-10-12 Thread rguenth at gcc dot gnu dot org
--- Comment #1 from rguenth at gcc dot gnu dot org 2009-10-12 12:49 --- I cannot parse what you are trying to say. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41681