Displaying 4 results from an estimated 4 matches for "getdrectvesection".
2013 Jan 16
0
[LLVMdev] RFC: auto-linking IR proposal
...&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:\"";
+ name += *I;
+ name += "\"";
+ OutStreamer.EmitBytes(name, 0);
+ }
+...
2010 May 07
3
[LLVMdev] MCStreamer interface
On Wed, 2010-05-05 at 13:22 -0700, Nathan Jeffords wrote:
>
> The important point here is that the COFF MCSection needs to
> have the right level of semantic information. In fact,
> MCSection is the place that I'd start for COFF bringup.
>
> OK, I see that now. The current isolation
> between TargetLoweringObjectFile ->
2013 Jan 16
2
[LLVMdev] RFC: auto-linking IR proposal
...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:\"";
> + name += *I;
> + name += "\"";
> + OutStreame...
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