Relative Content

Tag Archive for cgcc

Functionally achieve –ffunction-sections from assembly

I’m linking against a static library that I don’t have the original source code to, and it’s absolutely critical that I produce the smallest binary. Although unused .text sections from this library get stripped, if (e.g.) there’s a .o containing even a single function that my code uses, then the entire .text section of that object gets linked into the final executable. Is there a way to link more selectively?

Functionally achieve –ffunction-sections from assembly

I’m linking against a static library that I don’t have the original source code to, and it’s absolutely critical that I produce the smallest binary. Although unused .text sections from this library get stripped, if (e.g.) there’s a .o containing even a single function that my code uses, then the entire .text section of that object gets linked into the final executable. Is there a way to link more selectively?

Functionally achieve –ffunction-sections from assembly

I’m linking against a static library that I don’t have the original source code to, and it’s absolutely critical that I produce the smallest binary. Although unused .text sections from this library get stripped, if (e.g.) there’s a .o containing even a single function that my code uses, then the entire .text section of that object gets linked into the final executable. Is there a way to link more selectively?

Functionally achieve –ffunction-sections from assembly

I’m linking against a static library that I don’t have the original source code to, and it’s absolutely critical that I produce the smallest binary. Although unused .text sections from this library get stripped, if (e.g.) there’s a .o containing even a single function that my code uses, then the entire .text section of that object gets linked into the final executable. Is there a way to link more selectively?

Functionally achieve –ffunction-sections from assembly

I’m linking against a static library that I don’t have the original source code to, and it’s absolutely critical that I produce the smallest binary. Although unused .text sections from this library get stripped, if (e.g.) there’s a .o containing even a single function that my code uses, then the entire .text section of that object gets linked into the final executable. Is there a way to link more selectively?

Functionally achieve –ffunction-sections from assembly

I’m linking against a static library that I don’t have the original source code to, and it’s absolutely critical that I produce the smallest binary. Although unused .text sections from this library get stripped, if (e.g.) there’s a .o containing even a single function that my code uses, then the entire .text section of that object gets linked into the final executable. Is there a way to link more selectively?