This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Transactional memory in MinGW
- From: Ian Lance Taylor <iant at google dot com>
- To: niXman <i dot nixman at gmail dot com>
- Cc: gcc-help at gcc dot gnu dot org
- Date: Tue, 03 Apr 2012 06:55:17 -0700
- Subject: Re: Transactional memory in MinGW
- References: <CAMPTgK3R-s=65ALm=HfpTAgJ002wKOg8RZC0aZBqLz1N9oS+uw@mail.gmail.com> <mcrehsad80b.fsf@dhcp-172-18-216-180.mtv.corp.google.com> <CAMPTgK0u=m2Nw8G0cmF1Xd38_TvAJ8Q15yR1x9L5kbOp4O2QfQ@mail.gmail.com> <4F776919.6030000@gmail.com> <CAMPTgK06tzopwmFuqS9Z7VVSXH0X22_ohg==D7USA6oGekg4QA@mail.gmail.com>
niXman <i.nixman@gmail.com> writes:
> 2012/4/1 Ãngel GonzÃlez:
>> On 30/03/12 13:36, niXman wrote:
>>> I created the bug-report: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52787
>>>
>>> I think there is still hope to make Transactional Memory work in MinGW.
>> Sure, it shouldn't be too hard, but it obviously needs work.
>> Kai Tietz said in the bug that "You have to make sure that pthread-API is
>> present, as libitm depends on pthread."
>
> The pthreads library is built and works as expected. The problem is
> something else.
> Also, in the builds that I use [1], everything that is implemented in
> the "std concurrency" at the moment works well. And this confirms the
> fact that the pthreads library works.
> Just as I said earlier, with my little patch for libitm, libitm builds
> successfully. And again, as I said earlier, the code that uses the TM
> also is compiled and linked successfully.
>
> Someone can tell where I should look for the problem?
Debug your program and find out where it is failing.
You want to do something that is explicitly unsupported. Now you need
to figure out how to make it work. Maybe it will be easy, maybe it will
be hard. I don't know.
Ian