Displaying 3 results from an estimated 3 matches for "lib_siz".
Did you mean:
lib_size
2013 Jan 16
0
[LLVMdev] RFC: auto-linking IR proposal
...t/X86/X86AsmPrinter.cpp (working copy)
@@ -641,6 +641,19 @@
const TargetLoweringObjectFileCOFF &TLOFCOFF =
static_cast<const TargetLoweringObjectFileCOFF&>(getObjFileLowering());
+ // Output linker support code for #pragma comment(lib, ...) on Windows
+ if (M.lib_size() > 0 && Subtarget->isTargetWindows()) {
+ OutStreamer.SwitchSection(TLOFCOFF.getDrectveSection());
+ SmallString<128> name;
+ for (Module::lib_iterator I = M.lib_begin(), E = M.lib_end();
+ I != E; ++I) {
+ name = " /DEFAULTLIB:\""...
2013 Jan 16
2
[LLVMdev] RFC: auto-linking IR proposal
...> copy)
> @@ -641,6 +641,19 @@
> const TargetLoweringObjectFileCOFF &TLOFCOFF =
> static_cast<const
> TargetLoweringObjectFileCOFF&>(getObjFileLowering());
>
> + // Output linker support code for #pragma comment(lib, ...) on Windows
> + if (M.lib_size() > 0 && Subtarget->isTargetWindows()) {
> + OutStreamer.SwitchSection(TLOFCOFF.getDrectveSection());
> + SmallString<128> name;
> + for (Module::lib_iterator I = M.lib_begin(), E = M.lib_end();
> + I != E; ++I) {
> + name = "...
2013 Jan 15
4
[LLVMdev] RFC: auto-linking IR proposal
Hi all,
We plan to add some auto-linking support for Mach-O, and need a scheme for
encoding this information in the LLVM IR. We would like the same scheme to
be able to support Microsoft's #pragma comment(lib,...) and #pragma
comment(library, ...) features eventually.
The current proposal is as follows:
--
#1. Extend module-level metadata flags (llvm.module.flags) to support two
new