Re: cl4d OpenCL wrapper moved to Github
Those guys do know how to create useless exception messages o.O Well can't investigate this further at the moment.
Re: cl4d OpenCL wrapper moved to Github
On Tue 10-Jan 3:29, Trass3r wrote: Does this one work? http://www.cmsoft.com.br/index.php?option=com_content&view=category&layout=blog&id=99&Itemid=150 Simply running the bin/Debug/CLGLInterop.exe included in the zip produces ** Exception Text ** Cloo.BuildProgramFailureComputeException: Error in the application. at Cloo.ComputeException.ThrowOnError(ComputeErrorCode error) at Cloo.ComputeProgram.Build(ICollection`1 devices, String options, ComputeProgramBuildNotifier notify, IntPtr notifyDataPtr) at CLGLInterop.Form1.glControl1_Load(Object sender, EventArgs e) in D:\Programacao\OpenCL\Tutorial\CLGLInterop\CLGLInterop\Form1.cs:line 184 at System.Windows.Forms.UserControl.OnLoad(EventArgs e) at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) at System.Windows.Forms.Control.CreateControl() at System.Windows.Forms.Control.WmShowWindow(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ** Loaded Assemblies ** mscorlib Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5448 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll CLGLInterop Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/CLGLInterop/bin/Debug/CLGLInterop.exe System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5446 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5447 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll OpenTK.GLControl Assembly Version: 1.0.0.201 Win32 Version: 1.0.0.201 CodeBase: file:///C:/CLGLInterop/bin/Debug/OpenTK.GLControl.DLL OpenTK Assembly Version: 1.0.0.201 Win32 Version: 1.0.0.201 CodeBase: file:///C:/CLGLInterop/bin/Debug/OpenTK.DLL Cloo Assembly Version: 0.7.1.0 Win32 Version: 0.7.1 CodeBase: file:///C:/CLGLInterop/bin/Debug/Cloo.DLL
Re: cl4d OpenCL wrapper moved to Github
Does this one work? http://www.cmsoft.com.br/index.php?option=com_content&view=category&layout=blog&id=99&Itemid=150
Re: cl4d OpenCL wrapper moved to Github
The CLGLInterop example however still just gives a black window. It only outputs the FPS in cmdline. any error messages? compile it in debug mode with -debug -g. None that I can see. Hmm I'm not sure if I ever tested the code on Windows. The version(Windows) stuff looks ok though. I guess one would have to investigate this with something like http://www.gremedy.com
Re: cl4d OpenCL wrapper moved to Github
On Tue 10-Jan 1:23, Trass3r wrote: The vectorAdd example works perfectly, without any editing (ie. without removing the mixin(CL_PROGRAM_STRING_DEBUG_INFO)). How strange, does pragma(msg, CL_PROGRAM_STRING_DEBUG_INFO); give different results for the two dmd revisions? The CLGLInterop example however still just gives a black window. It only outputs the FPS in cmdline. any error messages? compile it in debug mode with -debug -g. None that I can see. C:\cl4d\CLGLInterop.exe copied cl_platform_id 920C4F4. Reference count is now: 0 wrapped cl_context A5671A8 releasing cl_platform_id 920C4F4. Reference count before: 0 copied cl_platform_id 920C4F4. Reference count is now: 0 releasing cl_platform_id 920C4F4. Reference count before: 0 copied cl_context A5671A8. Reference count is now: 2 wrapped cl_mem A5789A8 releasing cl_context A5671A8. Reference count before: 2 copied cl_mem A5789A8. Reference count is now: 2 releasing cl_mem A5789A8. Reference count before: 2 copied cl_context A5671A8. Reference count is now: 2 wrapped cl_mem A49F8C8 releasing cl_context A5671A8. Reference count before: 2 copied cl_mem A49F8C8. Reference count is now: 2 releasing cl_mem A49F8C8. Reference count before: 2 copied cl_context A5671A8. Reference count is now: 2 wrapped cl_mem 44EEC38 releasing cl_context A5671A8. Reference count before: 2 copied cl_context A5671A8. Reference count is now: 2 wrapped cl_program A642850 releasing cl_context A5671A8. Reference count before: 3 copied cl_program A642850. Reference count is now: 2 copied cl_device_id 44276B0. Reference count is now: 0 releasing cl_device_id 44276B0. Reference count before: 0 releasing cl_program A642850. Reference count before: 2 copied cl_program A642850. Reference count is now: 2 wrapped cl_kernel A608008 releasing cl_program A642850. Reference count before: 3 copied cl_mem A5789A8. Reference count is now: 2 copied cl_mem A49F8C8. Reference count is now: 2 copied cl_mem 44EEC38. Reference count is now: 2 copied cl_mem A5789A8. Reference count is now: 3 copied cl_mem A5789A8. Reference count is now: 4 releasing cl_mem A5789A8. Reference count before: 4 releasing cl_mem A5789A8. Reference count before: 3 copied cl_mem A49F8C8. Reference count is now: 3 copied cl_mem A49F8C8. Reference count is now: 4 releasing cl_mem A49F8C8. Reference count before: 4 releasing cl_mem A49F8C8. Reference count before: 3 copied cl_mem 44EEC38. Reference count is now: 3 copied cl_mem 44EEC38. Reference count is now: 4 releasing cl_mem 44EEC38. Reference count before: 4 releasing cl_mem 44EEC38. Reference count before: 3 releasing cl_mem A5789A8. Reference count before: 2 releasing cl_mem A49F8C8. Reference count before: 2 releasing cl_mem 44EEC38. Reference count before: 2 copied cl_context A5671A8. Reference count is now: 3 copied cl_device_id 44276B0. Reference count is now: 0 wrapped cl_command_queue 4436648 releasing cl_context A5671A8. Reference count before: 4 releasing cl_device_id 44276B0. Reference count before: 0 copied cl_device_id 44276B0. Reference count is now: 0 releasing cl_device_id 44276B0. Reference count before: 0 releasing cl_program A642850. Reference count before: 2 initialization done copied cl_mem A5789A8. Reference count is now: 2 copied cl_mem A49F8C8. Reference count is now: 2 wrapped cl_event A5594C0 copied cl_mem A5789A8. Reference count is now: 4 releasing cl_mem A5789A8. Reference count before: 3 copied cl_mem A49F8C8. Reference count is now: 4 releasing cl_mem A49F8C8. Reference count before: 3 releasing cl_event A5594C0. Reference count before: 2 copied cl_mem 44EEC38. Reference count is now: 2 wrapped cl_event 442DFE0 releasing cl_mem 44EEC38. Reference count before: 2 releasing cl_event 442DFE0. Reference count before: 1 etc.
Re: cl4d OpenCL wrapper moved to Github
The vectorAdd example works perfectly, without any editing (ie. without removing the mixin(CL_PROGRAM_STRING_DEBUG_INFO)). How strange, does pragma(msg, CL_PROGRAM_STRING_DEBUG_INFO); give different results for the two dmd revisions? The CLGLInterop example however still just gives a black window. It only outputs the FPS in cmdline. any error messages? compile it in debug mode with -debug -g.
Re: cl4d OpenCL wrapper moved to Github
On Mon 09-Jan 23:39, Klyn wrote: On Mon 09-Jan 14:24, Trass3r wrote: Well, I resorted to using bud and managed to get the vectorAdd example to compile, but when I run I get this error: btw, bud's not maintained anymore. Is this some kind of \ vs / bug? Try removing the mixin(CL_PROGRAM_STRING_DEBUG_INFO) ~ @ vectorAdd.d(36) Alright, that works! The vector example now gives the expected output. The CLGLInterop example however just gives a black window. By the way, just using your make.bat (with -d added) compiles fine now too. I finally compiled the HEAD dmd/druntime/phobos, so I'm now using your latest cl4d version. The make.bat compiles both examples just fine (with -d ofcourse). The vectorAdd example works perfectly, without any editing (ie. without removing the mixin(CL_PROGRAM_STRING_DEBUG_INFO)). The CLGLInterop example however still just gives a black window. It only outputs the FPS in cmdline.
Re: Announcements on D_Programming on twitter
On 1/9/2012 3:18 PM, Walter Bright wrote: If you wish to see your announcement on the D_Programming twitter feed, please make the first line one that can be copy/pasted into twitter. https://twitter.com/#!/D_Programming Or tweet about it yourself, and let us know so we can retweet it. Remember, having a great product is not enough. It needs a web page that says who/what/where/when/why/how for it, and you'll need to do some promotion. I know a lot of people get discouraged when the great product they created didn't arouse much interest, but often that is simply because people don't know about it. Make some noise, don't rely on others to do it for you.
Announcements on D_Programming on twitter
If you wish to see your announcement on the D_Programming twitter feed, please make the first line one that can be copy/pasted into twitter. https://twitter.com/#!/D_Programming
Re: cl4d OpenCL wrapper moved to Github
On Mon 09-Jan 14:24, Trass3r wrote: Well, I resorted to using bud and managed to get the vectorAdd example to compile, but when I run I get this error: btw, bud's not maintained anymore. Is this some kind of \ vs / bug? Try removing the mixin(CL_PROGRAM_STRING_DEBUG_INFO) ~ @ vectorAdd.d(36) Alright, that works! The vector example now gives the expected output. The CLGLInterop example however just gives a black window. By the way, just using your make.bat (with -d added) compiles fine now too.
Re: Visual D 0.3.30 released: Code completion from semantic analysis on the horizon
[snip] In "Options->Tools->Text Editor->D", there is a new sub page Or "Tools->Options->Text Editor->D->Intellisense" you mean. Tools and Options were around the wrong way. [snip]
Re: Visual D 0.3.30 released: Code completion from semantic analysis on the horizon
On 09-01-2012 19:59, Rainer Schuetze wrote: On 09.01.2012 17:04, Alex Rønne Petersen wrote: On 07-01-2012 15:41, Rainer Schuetze wrote: Hi, I'd like to announce the release of a new version of Visual D. Great news! How should the new experimental code completion be triggered, exactly? - Alex In "Options->Tools->Text Editor->D", there is a new sub page "Intellisense" with new options, including "Expansions from semantics" and "Show type of expression in tool tip". If you enable these, the first is triggered when hitting Ctrl+Space to show completions at the current insert position (most useful after a '.'), the latter will show the type of identifiers or complete expressions (if selected) in a tool tip. There is some type inference regarding auto and some code interpretation, working on some complex stuff (classes, nested functions) but also still failing on simple things like switch statements. Evaluation is currently as lazy as possible, i.e. even parsing is delayed until you request semantic information, but then cached for later use. So please excuse the current initial delay, I will probably move the parsing of imported files into a background thread. Seems to work, thanks! In the future, could we perhaps get an option to specify how aggressively code completion should be triggered? That is, manually (as it is now), when typing '.', or always (i.e. whenever you start typing)? - Alex
Re: Visual D 0.3.30 released: Code completion from semantic analysis on the horizon
On 09.01.2012 17:04, Alex Rønne Petersen wrote: On 07-01-2012 15:41, Rainer Schuetze wrote: Hi, I'd like to announce the release of a new version of Visual D. Great news! How should the new experimental code completion be triggered, exactly? - Alex In "Options->Tools->Text Editor->D", there is a new sub page "Intellisense" with new options, including "Expansions from semantics" and "Show type of expression in tool tip". If you enable these, the first is triggered when hitting Ctrl+Space to show completions at the current insert position (most useful after a '.'), the latter will show the type of identifiers or complete expressions (if selected) in a tool tip. There is some type inference regarding auto and some code interpretation, working on some complex stuff (classes, nested functions) but also still failing on simple things like switch statements. Evaluation is currently as lazy as possible, i.e. even parsing is delayed until you request semantic information, but then cached for later use. So please excuse the current initial delay, I will probably move the parsing of imported files into a background thread.
Re: Visual D 0.3.30 released: Code completion from semantic analysis on the horizon
On 07-01-2012 15:41, Rainer Schuetze wrote: Hi, I'd like to announce the release of a new version of Visual D. Visual D is a Visual Studio package providing both project management and language services for the D programming language. It works with Visual Studio 2005-2010 and 11 as well as the free Visual Studio Shells. Highlights of this version 0.3.30 include - syntax highlighting improvements regarding scope(guard), __ctfe, is, in and predefined versions - added checkbox for options -gs and -property to project configuration - debugger and build improvements - experimental: code completion and tool tips from semantic analysis of source code See http://www.dsource.org/projects/visuald/wiki/VersionHistory for a full list of changes. The code completion from semantic analysis is not complete yet, but I think it can already be very helpful. You'll have to enable it explicitly in the D Language options due to it's experimental status. The Visual D installer can be downloaded from its website at http://www.dsource.org/projects/visuald Have fun, Rainer Great news! How should the new experimental code completion be triggered, exactly? - Alex
Re: cl4d OpenCL wrapper moved to Github
Well, I resorted to using bud and managed to get the vectorAdd example to compile, but when I run I get this error: btw, bud's not maintained anymore. Is this some kind of \ vs / bug? Try removing the mixin(CL_PROGRAM_STRING_DEBUG_INFO) ~ @ vectorAdd.d(36)
DWT repository moved to github
I've moved the DWT repository to github. The old mercurial repository is split into several repository, all available under an organization: https://github.com/d-widget-toolkit The dwt repository acts like a super repository. It has git submodules for the base, SWT Linux and Windows and snippets projects. It also contains the build script. https://github.com/d-widget-toolkit/dwt Use these commands to clone the repository and get all submodules: $ git clone git://github.com/d-widget-toolkit/dwt.git $ git submodule init $ git submodule update -- /Jacob Carlborg
Re: DVM - D Version Manager 0.4.0
On 2012-01-09 10:14, Nick Sabalausky wrote: "Jacob Carlborg" wrote in message news:jee58o$54v$1...@digitalmars.com... On 2012-01-08 21:34, Nick Sabalausky wrote: "Jacob Carlborg" wrote in message news:jec1j6$2rbu$1...@digitalmars.com... * Move to github It's ultimately up to you, but personally I can't stand Github. My vote would be to stick with Bitbucket. Granted, I haven't actually tried Bitbucket's Git support yet. But just yesterday I started the process of converting a couple of my projects from SVN/Dsource to Git/Bitbucket, so we'll see how it goes, and I'll let you know. I'm asking you since you're the main contributor next to me. I prefer Github, many D project are moving to Github, DMD, Phobos and druntime are already there. But certainly don't want to push you away, that wouldn't be good for the Windows port :) While I would find github more painful, it wouldn't make me decrease my contributions to DVM. DVM's too important a tool, IMO (Much like RDMD, which I also contribute too). I'm glad to hear to. I'll have to think about it then. Heck, maybe if we're lucky that OSX desktop interface to github will someday get ported to Lin or Win :) I'm on my way to bed so I'll check out those links later. (FWIW, I don't think Ruby's all that bad as far as dynamic langauges go. Probably one of the best, actually. It's just no D ;) ) Hehe, ok. -- /Jacob Carlborg
Re: DVM - D Version Manager 0.4.0
On 2012-01-09 10:30, Don Clugston wrote: On 06/01/12 22:29, Jacob Carlborg wrote: I just released a new version of DVM, 0.4.0. The only thing new in this release in the "compile" command. This allows to compile DMD, druntime and Phobos from github. Create a folder, clone DMD, druntime and Phobos in the newly create folder, run "dvm compile folder" to compile everything. The compiler is placed in the DMD directory. For installation instructions see: https://bitbucket.org/doob/dvm Changelog: Version 0.4.0 New/Change Features * Added a "compile" command for compiling DMD, druntime and Phobos from github I found that I needed to do: cd .dvm mkdir bin before dvm install would work. Hmm, that's strange. On which platform? Is it when installing DVM itself or compilers? -- /Jacob Carlborg
Re: Visual D 0.3.30 released: Code completion from semantic analysis on the horizon
On 07.01.2012 15:41, Rainer Schuetze wrote: Hi, I'd like to announce the release of a new version of Visual D. Visual D is a Visual Studio package providing both project management and language services for the D programming language. It works with Visual Studio 2005-2010 and 11 as well as the free Visual Studio Shells. Highlights of this version 0.3.30 include - syntax highlighting improvements regarding scope(guard), __ctfe, is, in and predefined versions - added checkbox for options -gs and -property to project configuration - debugger and build improvements - experimental: code completion and tool tips from semantic analysis of source code See http://www.dsource.org/projects/visuald/wiki/VersionHistory for a full list of changes. The code completion from semantic analysis is not complete yet, but I think it can already be very helpful. You'll have to enable it explicitly in the D Language options due to it's experimental status. The Visual D installer can be downloaded from its website at http://www.dsource.org/projects/visuald Have fun, Rainer Wow thanks Rainer, this is a really cool release. the 'experimental' semantics are already awesome! now i want the completion-suggestions to tell me the types (method,member ..) with protection symbols ;) Big Kudos ! S.
Re: DVM - D Version Manager 0.4.0
On 06/01/12 22:29, Jacob Carlborg wrote: I just released a new version of DVM, 0.4.0. The only thing new in this release in the "compile" command. This allows to compile DMD, druntime and Phobos from github. Create a folder, clone DMD, druntime and Phobos in the newly create folder, run "dvm compile folder" to compile everything. The compiler is placed in the DMD directory. For installation instructions see: https://bitbucket.org/doob/dvm Changelog: Version 0.4.0 New/Change Features * Added a "compile" command for compiling DMD, druntime and Phobos from github I found that I needed to do: cd .dvm mkdir bin before dvm install would work.
Re: DVM - D Version Manager 0.4.0
"Jacob Carlborg" wrote in message news:jee58o$54v$1...@digitalmars.com... > On 2012-01-08 21:34, Nick Sabalausky wrote: >> "Jacob Carlborg" wrote in message >> news:jec1j6$2rbu$1...@digitalmars.com... >>> * Move to github >> >> It's ultimately up to you, but personally I can't stand Github. My vote >> would be to stick with Bitbucket. >> >> Granted, I haven't actually tried Bitbucket's Git support yet. But just >> yesterday I started the process of converting a couple of my projects >> from >> SVN/Dsource to Git/Bitbucket, so we'll see how it goes, and I'll let you >> know. > > I'm asking you since you're the main contributor next to me. I prefer > Github, many D project are moving to Github, DMD, Phobos and druntime are > already there. But certainly don't want to push you away, that wouldn't be > good for the Windows port :) > While I would find github more painful, it wouldn't make me decrease my contributions to DVM. DVM's too important a tool, IMO (Much like RDMD, which I also contribute too). Heck, maybe if we're lucky that OSX desktop interface to github will someday get ported to Lin or Win :) I'm on my way to bed so I'll check out those links later. (FWIW, I don't think Ruby's all that bad as far as dynamic langauges go. Probably one of the best, actually. It's just no D ;) )
Re: cl4d OpenCL wrapper moved to Github
On Mon 09-Jan 2:45, Trass3r wrote: Ok, so when i try to compile it says src\opencl\c\cl_d3d10.d(88): Error: undefined identifier UINT src\opencl\c\cl_d3d10.d(96): Error: undefined identifier UINT and upon changing those to uint I get src\opencl\c\cl_d3d11.d(77): Error: undefined identifier ID3D11Buffer src\opencl\c\cl_d3d11.d(84): Error: undefined identifier ID3D11Texture2D src\opencl\c\cl_d3d11.d(91): Error: undefined identifier ID3D11Texture3D What am I missing? Well the DirectX stuff isn't tested at all. I always compile with rdmd so these modules aren't compiled. The uint errors are small cases I overlooked. The rest is obvious: cl4d knows nothing about DirectX, so you need a binding. Maybe I should just turn these into void* to get rid of the errors, but then you loose type safety, hmm. Well, I resorted to using bud and managed to get the vectorAdd example to compile, but when I run I get this error: AMD Accelerated Parallel Processing Advanced Micro Devices, Inc. OpenCL 1.1 AMD-APP (831.4) FULL_PROFILE cl_khr_icd cl_amd_event_callback cl_amd_offline_devices cl_khr_d3d10_sharing Barts Advanced Micro Devices, Inc. CAL 1.4.1646 (VM) OpenCL 1.1 AMD-APP (831.4) FULL_PROFILE Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz GenuineIntel 2.0 OpenCL 1.1 AMD-APP (831.4) FULL_PROFILE Warnings being treated as errors C:\Users\abc\AppData\Local\Temp\OCLA2DA.tmp.cl(1): error: unrecognized character escape sequence #line 35 "src\main.d" ^ 1 error detected in the compilation of "C:\Users\abc\AppData\Local\Temp\OCLA2DA.tmp.cl". Internal error: clc compiler invocation failed. core.exception.AssertError@src\opencl\kernel.d(196): _object is null 42A6A8 42A51F 4039CD 40EE7C 40EEC0 40EAB7 4AC3A9 Is this some kind of \ vs / bug?
