Re: .EXE -> .ASM -> .EXE



"santosh" <santosh.k83@xxxxxxxxx> ???????/???????? ? ???????? ?????????:
Guga wrote:

[HUGE snip]
[..]

You really don't understand how a linker works, do you?
Just so you know, a linker will only include those object modules that
the application uses. It does *not* include *all* the code in the
library into your application. No wonder you think LIBs are bad; you're
operating under a serious misconception here.

I think they've been "scarred" by seeing certain statically linked
C/C++ executables. When you ask for static linking, sometimes the
entire libc is linked with your program resulting in a 800 kB hello
world demo. Similarly heavy use of templates can blow up a C++
executable to a megabyte or more.

I wonder what you're worrying about.

If i have a pretty big application, i will never bother about *trivial* routine parts of it. I want to use hand assembly only for some parts of code, which are *critical*
for speed and efficiency (of a secondary, to override the HLL syntax limitations). That's why a convenient way to mix of hll+asm is desirable.

Of course runtime linking solves the problem...

Producing another problem with "version compatibility".
The golden mean resides not at the edge..
.



Relevant Pages

  • Re: understanding statically-linked binaries
    ... > If 'ldd' can show you what libs an executable is dynamically linked ... is there a way to determine after the fact what libs a given ... > OpenSSL (without using RPMs). ... With some clue about how executables are linked together on your ...
    (comp.unix.programmer)
  • Re: 64 bit imagemagick
    ... Frank Liu writes: ... But the imagemagick lib is 32 bit only. ... just copying the libs it creates ... executables, ...
    (comp.unix.solaris)
  • Re: copy a list in 1 instruction
    ... screw things up if you have done static linking with LIBs for 1+ ... You need to link with the same RTL in DLL form for both executables or make ... the damage shows up. ...
    (microsoft.public.vc.stl)
  • Re: Autorun.inf
    ... different executables are run for different operating ... depending on whether they are using win98 and xp. ...
    (microsoft.public.windowsxp.basics)
  • Re: Autorun.inf
    ... different executables are run for different operating ... depending on whether they are using win98 and xp. ...
    (microsoft.public.windowsxp.basics)