[DynInst_API:] [dyninst/dyninst] 55d04a: ParseData::record_block should not need locking. W...


Date: Fri, 29 Jun 2018 08:54:37 -0700
From: Xiaozhu Meng <xmeng@xxxxxxxxxxx>
Subject: [DynInst_API:] [dyninst/dyninst] 55d04a: ParseData::record_block should not need locking. W...
  Branch: refs/heads/new-parallel-parsing
  Home:   https://github.com/dyninst/dyninst
  Commit: 55d04addfc93bf505915f734517ebc6e8adc2475
      https://github.com/dyninst/dyninst/commit/55d04addfc93bf505915f734517ebc6e8adc2475
  Author: Xiaozhu Meng <xmeng@xxxxxxxxxxx>
  Date:   2018-06-29 (Fri, 29 Jun 2018)

  Changed paths:
    M parseAPI/src/ParseData.C
    M parseAPI/src/ParseData.h
    M parseAPI/src/Parser.C
    M parseAPI/src/Parser.h

  Log Message:
  -----------
  ParseData::record_block should not need locking. We should rely on the return value of concurrent_hash_map::insert to determine which thread succeeds in inserting and which threads failed. The failed threads should just use the already inserted block and give up insertion



      **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/

      Functionality will be removed from GitHub.com on January 31st, 2019.
[← Prev in Thread] Current Thread [Next in Thread→]
  • [DynInst_API:] [dyninst/dyninst] 55d04a: ParseData::record_block should not need locking. W..., Xiaozhu Meng <=