This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libitm/52787] Segmentation fault on MinGW
- From: "ktietz at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 30 Mar 2012 20:15:13 +0000
- Subject: [Bug libitm/52787] Segmentation fault on MinGW
- Auto-submitted: auto-generated
- References: <bug-52787-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52787
Kai Tietz <ktietz at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |ktietz at gcc dot gnu.org
Resolution| |INVALID
--- Comment #3 from Kai Tietz <ktietz at gcc dot gnu.org> 2012-03-30 20:15:13 UTC ---
(In reply to comment #2)
> >Based to your e-mail on gcc-help, you left out a very important piece of
> information.
> Yes, Ian. I had to mention it.
> And yes, I'm not saying that libitm is supported by MinGW. And yes, as libitm
> is not supported by MinGW - it's not a bug. I hurried with the creation of the
> bug report.
>
> I'd really like to make libitm work with MinGW. I would like to understand why
> SIGSEGV occurs...
>
> Thanks.
Well, the configure patch required for this bug-report misses an important part
AFAICS. You have to make sure that pthread-API is present, as libitm depends
on pthread.
This report is btw invalid, as this feature isn't supported for mingw targets
right now. So I close it. Please keep discussion about adding support for
libitm on gcc's patches ML.