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: small fixes for libunwind support


>>>>> On 11 Dec 2003 17:01:33 -0800, Jim Wilson <wilson@specifixinc.com> said:

  Jim> On Thu, 2003-12-11 at 16:23, Gabriel Dos Reis wrote:
  >> | Jim> It wouldn't hurt.

  Jim> Actually, it does.  The build on my machine failed with libjava
  Jim> link errors.

  Jim> I have libunwind 0.95 installed which does not contain
  Jim> _Unwind_Resume and related routines.  Configure should have
  Jim> picked the t-libunwind-no-eh file.  Unfortunately, it picks
  Jim> t-libunwind.

  Jim> The problem is with the configure test.  AC_CHECK_LIB does a
  Jim> link, and gcc links in -lgcc_eh as it always does, so of course
  Jim> _Unwind_Resume is there regardless of whether libunwind has it.
  Jim> We don't have a convenient way to link without -lgcc_eh, we
  Jim> would have to modify the libgcc spec, and add a new option, and
  Jim> that doesn't seem to be very useful.  Maybe there is a
  Jim> different kind of autoconf test we can use?  I don't have a
  Jim> good solution at the moment.

Argh.  Would anybody get mad if we just dropped libunwind support for
versions older than v0.96?  I suspect that at the moment, this would
impact only a handful of developers and for those should be able to
upgrade to v0.96 easily.

If we can drop support for older versions, we can just remove the
configure check and t-libunwind-no-eh.

	--david


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