Re: Strange behaviour of linker (vc++)
From: Philip Lawatsch (philip_at_waug.at)
Date: 09/27/04
- Next message: Arnie Mauer: "Re: Can objects have properties?"
- Previous message: Igor Tandetnik: "Re: Strange behaviour of linker (vc++)"
- In reply to: Igor Tandetnik: "Re: Strange behaviour of linker (vc++)"
- Next in thread: Sigurd Stenersen: "Re: Strange behaviour of linker (vc++)"
- Reply: Sigurd Stenersen: "Re: Strange behaviour of linker (vc++)"
- Reply: Igor Tandetnik: "Re: Strange behaviour of linker (vc++)"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 27 Sep 2004 20:21:03 +0200
Igor Tandetnik wrote:
> You can force an inclusion of the symbol with /INCLUDE linker command
> line option, but that kinda defeats the purpose.
Well, I disagree. At least partially. I suppose one has reasons as to
why one would initialise a static variable via a function.
Anyway, I have tons of such things and they work fine with g++. So, is
there anything I can do to force all "dead" code into my binary? Its not
reasonable to specify every symbol per hand, this is hell a lot of work.
> Needed how? As far as linker is concerned, no outside module ever
> references this symbol, so it does not need to be included.
Yea, but there is a function wich initialises a static in there. This
function references outside stuff. So imo the linker should not discard it.
kind regards Philip
- Next message: Arnie Mauer: "Re: Can objects have properties?"
- Previous message: Igor Tandetnik: "Re: Strange behaviour of linker (vc++)"
- In reply to: Igor Tandetnik: "Re: Strange behaviour of linker (vc++)"
- Next in thread: Sigurd Stenersen: "Re: Strange behaviour of linker (vc++)"
- Reply: Sigurd Stenersen: "Re: Strange behaviour of linker (vc++)"
- Reply: Igor Tandetnik: "Re: Strange behaviour of linker (vc++)"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|