From: <fo...@sm...> - 2008-08-16 08:27:03
|
I have already emailed him to talk about that but unfortunately I don't have enough skills to help him correctly. I am just trying to understand SEH on arm/mips platforms and it's not always easy when you don't speak ASM fluently ;-) By the way do you know the status of his work ? The GSoc is supposed to finish on August 18, 2008 ... Will it be incorporated into next GCC version ? About mingw development will you patch and keep a GCC/mingw for a long time as you did with gcc-3.4.5 or will you follow GCC release and update it more often ? I mean if tomorrow GCC 4.3.2 is released will you release a new testing mingw version or will you keep on trying to stabilizise GCC 4.3.0 ? On Fri, 15 Aug 2008 21:23:05 -0400, NightStrike <nig...@gm...> wrote: > On 8/15/08, fo...@sm... <fo...@sm...> wrote: >> On Fri, 15 Aug 2008 12:08:32 -0400, NightStrike <nig...@gm...> >> wrote: >> > On 8/14/08, fo...@sm... <fo...@sm...> wrote: >> >> 3) I have creatd a company specialized in embedded developments and I >> > would >> >> like to propose an internship about implementing SEH eceptions >> >> in GCC, I know that has been done before but it was not incorporated >> > into >> >> main development line because of legal issues and other kind of > reasons. >> >> Does SEH would really improved mingw ? >> > >> > Aaron is currently working on this. >> > >> Unfortunately I am interested in the windows CE version of mingw (called >> mingw32ce) and part of the cegcc project. >> Aaron seems to work on SEH exception but as he wrote : >> >> "Regarding exceptions on Win64, I think its non-easy to fix exceptions >> here, and my approach for Win32 foreign frames won't work, because Win64 >> SEH is completely different. >> I've found belatedly thats whats really needed to resolve the exception >> issues on Win32 and Win64 is a partial SEH implementation--nontrivial in >> the latter case (for Win64)." >> >> The problem with SEH exceptions on i386-32bits comes from the fact it > works >> on a per-thread basis via the TIB structure and in the case of >> x86, the FS register always points to the current TIB. >> On other architecture (x86-64 bits, MIPS or ARM in my case), you cannot >> rely on FS register so SEH exceptions handling is stored in the .pdata >> section of the binary. >> >> So i think all this work will only benefit x86 architecture. > > > My apologies, I wasn't clear in my post. What I meant to say was that > I'm sure you could offer any support to Aaron, not to say that his > efforts would encompass all that is required. > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the > world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > MinGW-users mailing list > Min...@li... > > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users |