singa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SINGA-301) Hardcode OpenCL source code as static strings
Date Tue, 21 Feb 2017 06:50:44 GMT

    [ https://issues.apache.org/jira/browse/SINGA-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875457#comment-15875457
] 

ASF subversion and git services commented on SINGA-301:
-------------------------------------------------------

Commit f6cf8f5d6384452e03ab03ffa65d8ec8aa87d669 in incubator-singa's branch refs/heads/master
from wangwei
[ https://git-wip-us.apache.org/repos/asf?p=incubator-singa.git;h=f6cf8f5 ]

SINGA-301 Hardcode OpenCL source code as static strings

Merge all xxx_str.cpp file into a single file in src/core/device/opencl_func.h.
Replace the global string for opencl functions with global constant string in singa::opencl
Add license headers for new files.

The python script should only be executed if .cl files are updated or
new .cl file is added.


> Hardcode OpenCL source code as static strings
> ---------------------------------------------
>
>                 Key: SINGA-301
>                 URL: https://issues.apache.org/jira/browse/SINGA-301
>             Project: Singa
>          Issue Type: Improvement
>          Components: Core
>         Environment: All
>            Reporter: Tan Li Boon
>            Priority: Minor
>
> Currently, OpenCL kernel source code is a standalone file. This may be problematic as
the SINGA executable will fail to find the source code if it is run from outside a few places.
> This issue will discuss a way to turn the source code into static strings somehow, at
compile-time.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message