This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: update dwarf2 asm unwind info [hppa64-*-* failures]

Steve Ellcey <sje@cup.hp.com> writes:

> I think you are right, if I do a static link with the old compiler (HP
> linker in verbose mode), all of the .eh_frame sections seem to have the
> write flag set.  With the new code, most of the sections have write set
> but the objects coming from libgcc (moddi3, divdi3, emutls, unwind-dw2,
> and unwind-dw2-fde) as well as cp-demangle from libstdc++ do not have
> the write flag set.  Other objects from libstdc++ (vterminate,
> pbase_type_info, eh_call, class_type_info, etc.) do have the write flag
> set.

That sounds like HAVE_LD_RO_RW_SECTION_MIXING was set incorrectly by
the configure script.

Ian
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]