[jira] Updated: (HARMONY-4027) [drlvm][object][tc]Known/proven race conditions markup at \vm\vmcore\src\object\vm_arrays.cpp at vm_anewarray_resolved_array_type function.

["Ilya Leviev (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HARMONY-4027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ilya Leviev updated HARMONY-4027:
---------------------------------

    Attachment: HARMONY-4027_add_markup.patch

> [drlvm][object][tc]Known/proven race conditions markup at \vm\vmcore\src\object\vm_arrays.cpp at vm_anewarray_resolved_array_type function.
> -------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HARMONY-4027
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4027
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Ilya Leviev
>         Attachments: HARMONY-4027_add_markup.patch
>
>
> Known/proven race condition markup at \vm\vmcore\src\object\vm_arrays.cpp at vm_anewarray_resolved_array_type function.
> TC report on thread unsafe access that result in race conditions that occur during execution of vm_anewarray_resolved_array_type function.
> Data-races: 
> Memory read at "vm_arrays.cpp":67 conflicts with a prior memory write at "vm_arrays.cpp":67
> As issue related to vm statistic data collection in debug mode and it not affect correctness of execution I mark it by special API for prevention of further alarms on this race. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.