------- Additional Comments From ebotcazou at gcc dot gnu dot org 2007-10-02 18:19 ------- > But only if you are using constant data structures. (That need to be > auto-imported ?) And only if the user did not put --enable-auto-import on > their command line.
Constant data structures referencing symbols from auto-imported DLLs. Note that GCC doesn't downgrade them to writable memory in spite of the runtime relocations (the mechanism to that effect is not enabled for PE-COFF). > The point is, I worry about the bugs that will be caused by putting read > only data into the read/write data section. (Or maybe the bugs that will > not be caught by so doing). This fix for auto-import is a hack and I would > really prefer it if it was not the linker's default behaviour. Not very different from making the code entirely writable. The head comment in pe-dll.c even says that this doesn't conform to the PE-COFF specs. > So to me, providing a warning message and telling the user of the command > line option that they ought to be using is an acceptable compromise. If a > programmer's app starts to seg fault, then one thing they ought to do is go > back over the build logs and look for any messages from the compiler and > linker telling them of potential problems. All right, this makes sense. -- http://sourceware.org/bugzilla/show_bug.cgi?id=4844 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
