--
What|Removed |Added
CC||tuttle at bbs dot cvut dot
||cz
http://sources.redhat.com/bugzi
--
What|Removed |Added
CC||tuttle at bbs dot cvut dot
||cz
http://sources.redhat.com/bugzi
Hi Brian,
Anyone have any information about what work may have been done on a true
incremental link mode?
Sorry - as far as I know noone has done any work on this.
Anyone have any comments, wish lists, or warnings about how to go about
potentially implementing it?
There are probably several resea
minor, but ld docs not built in own sub-directory as done for bfd/gas/etc.
(not a big deal, but felt compelled to note it)
--
Summary: minor, but ld docs not built in own sub-directory as
done for bfd/gas/etc.
Product: binutils
Version: unspec
when linking a DLL with a .DEF file, if the BASE directive in the .DEF
file is not of the form "BASE=0x1c00" but e.g. "BASE 0x1c00" or
some other malformatting, ld crashes with a memory access violation.
--
Summary: ld 2.13.90 from mingw 3.3.1 cores on malformatted .def
If a .def file is used to link a DLL, the --image-base and
--enable-auto-image-base options are silently disregarded,
even if the .def file is missing a BASE directive. The
correct behavior should probably be that --image-base should
override the .def file, and --enable-auto-image-base should overr
