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: [patch i386 mingw]: Disallow DW2 unwind for 64-bit and multilib

From: Jason Merrill <jason at redhat dot com>
To: Kai Tietz <ktietz70 at googlemail dot com>
Cc: Arnaud Charlet <charlet at adacore dot com>, Kai Tietz <Kai dot Tietz at onevision dot com>, gcc-patches at gcc dot gnu dot org, Danny Smith <dansmister at gmail dot com>
Date: Tue, 25 Aug 2009 11:10:17 -0400
Subject: Re: [patch i386 mingw]: Disallow DW2 unwind for 64-bit and multilib
Newsgroups: gmane.comp.gcc.patches
References: <OF3CA70618.D31850D1-ONC12575FD.0029540F-C12575FD.002A43EA@onevision.de> <20090724074444.GA89302@adacore.com> <90baa01f0907240055k1be7900cjb9900c893ba52faf@mail.gmail.com>

On 07/24/2009 03:55 AM, Kai Tietz wrote:

2009/7/24 Arnaud Charlet<charlet@adacore.com>:

BTW, do you know how hard it would be to get dwarf2 unwind based exceptions
working on 64 bit windows? What are the missing/blocking points?


The major issue is that the current implementation is using code
analysis for finding frame information. This is for x64 even harder
then for x86 as there much more possibilities of prologue entries.

How is this different from other x86_64 targets?

Jason

Follow-Ups:
- Re: [patch i386 mingw]: Disallow DW2 unwind for 64-bit and multilib
  - From: Kai Tietz

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