to existing programs per se, as that code
can be compiled separately and linked together with any existing or
even precompiled code to get the desired result, as crt0 will call the
__attribute__((constructor)) function before it calls main()
cheers
Eric
--
Eric Price
TTI GmbH - TGU Smartmote
no sense
cheers
Eric
--
Eric Price
TTI GmbH - TGU Smartmote
Pfaffenwaldring 4
D-70569 Stuttgart
Tel.: +49 0711 - 6856 5369
Fax.: +49 0711 - 6856 6818
E-mail: pr...@smartmote.de
Homepage: http://www.smartmote.de
On Mon, 8 Dec 2014 16:55:04 + (UTC)
Grant Edwards grant.b.edwa...@gmail.com wrote:
On 2014-12-08, Eric Price pr...@smartmote.de wrote:
to me the change to the TI linker scripts simply makes no sense
None at all. It seems to be assuming that an MSP430 is running some
sort of OS
/Redhat
compiler released in the middle of the year.
As far as I could see so far these linker warnings can be safely
ignored, the resulting code still works and is still significantly
smaller than without -flto and --gc-sections
hope that helps.
cheers
Eric
--
Eric Price
TTI GmbH - TGU
();
function2();
exit 0;
}
then these two simplified programs both did not trigger it:
int main() {
function1();
/* function2(); */
exit 0;
}
int main() {
/* function1(); */
function2();
exit 0;
}
--
Eric Price
TTI GmbH - TGU Smartmote
On Wed, 17 Dec 2014 17:04:08 +
Nicholas Clifton ni...@redhat.com wrote:
Hang on - you say that you are getting this message during
*linking* ? The error message comes from the compiler, not the
linker, so why is it turning up in the linker's output ? Do you have
LTO enabled ? (If you
