harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ilya Berezhniuk (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-5504) [drlvm][port] Restructure DRLVM's sources to extract most of platform dependent code into portlib
Date Mon, 18 Feb 2008 03:04:34 GMT

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

Ilya Berezhniuk updated HARMONY-5504:
-------------------------------------

    Attachment: 0008-VM-memory-barriers-was-moved-to-PORT-as-inline.txt

'0008' patch moves memory barriers from vmcore/src/thread/linux and vmcore/src/thread/win
to PORT.

After applying the patch these two folders can be removed with their contents.

> [drlvm][port] Restructure DRLVM's sources to extract most of platform dependent code
into portlib
> -------------------------------------------------------------------------------------------------
>
>                 Key: HARMONY-5504
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5504
>             Project: Harmony
>          Issue Type: Task
>          Components: DRLVM
>         Environment: All
>            Reporter: Gregory Shimansky
>            Assignee: Gregory Shimansky
>         Attachments: 0001-Added-standalone-crash-handler-header-and-basic-infr.patch,
0002-move-moved-LIL-files-from-PORT-to-VMCORE.txt, 0003-corrected-build-for-moved-LIL.txt,
0004-moved-register-context-structure-to-open.txt, 0005-move-moved-native_modules-from-VMCORE-to-PORT.txt,
0006-native_modules-are-adopted-for-using-in-PORT.txt, 0007-Added-frame-info-header-for-iteration-in-compiled-st.patch,
0008-VM-memory-barriers-was-moved-to-PORT-as-inline.txt
>
>
> There is a code freeze, so I decided to create a working place for my patches for DLRVM's
port library in JIRA.
> The goal of this task is to separate DRLVM's platform dependent code from VM sources
into multiple subcategories of port library. Such platform dependent code is crash handler,
stack iteration, signals/exception handlers, modules tables, NCAI safe memory access and probably
some more stuff that I didn't identify yet.
> Such separation will define clear interfaces, possibly some components could be reused
by other projects.

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


Mime
View raw message