Displaying 4 results from an estimated 4 matches for "data_cygwin_nocopy".
2018 Feb 08
2
LLD: targeting cygwin
...}
/* The Cygwin32 library uses a section to avoid copying certain data
on fork. This used to be named ".data". The linker used
to include this between __data_start__ and __data_end__, but that
breaks building the cygwin32 dll. Instead, we name the section
".data_cygwin_nocopy" and explicitly include it after __data_end__. */
.data BLOCK(__section_alignment__) :
{
__data_start__ = . ;
*(.data)
*(.data2)
*(SORT(.data$*))
KEEP(*(.jcr))
__data_end__ = . ;
*(.data_cygwin_nocopy)
}
.rdata BLOCK(__section_alignment__) :
{
*(.rdata...
2018 Feb 09
0
LLD: targeting cygwin
...2 library uses a section to avoid copying certain data
> on fork. This used to be named ".data". The linker used
> to include this between __data_start__ and __data_end__, but that
> breaks building the cygwin32 dll. Instead, we name the section
> ".data_cygwin_nocopy" and explicitly include it after __data_end__. */
> .data BLOCK(__section_alignment__) :
> {
> __data_start__ = . ;
> *(.data)
> *(.data2)
> *(SORT(.data$*))
> KEEP(*(.jcr))
> __data_end__ = . ;
> *(.data_cygwin_nocopy)
> }
>...
2018 Feb 07
0
LLD: targeting cygwin
COFF lld doesn't support the linker script at the moment, and I'm sad to
say that it is very unlikely to support that in the future. Linker script
support is so huge that I can't imagine we really want it for COFF. GNU BFD
linker supports it because the linker is built as an interpreter for the
built-in linker script (and that's one of the reasons why GNU linker is by
far more
2018 Feb 07
2
LLD: targeting cygwin
Hello, I have a user who is trying to get LLD to link for the cygwin
target: https://github.com/zig-lang/zig/issues/751
Currently the issue they are running into is needing to define a linker
script, but the COFF driver (or MinGW driver) does not have support for
that.
Is there documentation or advice for how to use LLD to link for cygwin? As
a starting point, which driver to use?
Regards,