nvidia

Handling Ctrl+C exception with GPU

北慕城南 提交于 2019-12-23 02:54:08
问题 I am working with some GPU programs (using CUDA 4.1 and C), and sometimes (rarely) I have to kill the program midway using Ctrl+C to handle some exception. Earlier I tried using CudaDeviceReset() function, but this reply by talonmies displaced my trust in CudaDeviceReset() and hence I started handling such exceptions the Old-Fashioned way, that is 'computer restart'. As the project size grows, this method is becoming a headache. I would appreciate if anyone has come up with a better solution.

Why does this crash when using OpenGL core profile?

柔情痞子 提交于 2019-12-22 10:54:24
问题 When I try to run this simple OpenGL test program I get a segmentation fault. This only happens when I create the context using the core profile flag. If I use the compatibility profile flag, the program runs without issue. Edit: I checked the pointer to the function glGenVertexArrays and it returned NULL . If glfwCreateWindow doesn't return NULL , and glGetString(GL_VERSION) confirms that the context is version 4.3 and glewInit returns GLEW_OK then why is glGenVertexArrays == NULL ? My OS is

wglCreateContextAttribsARB fails on NVIDIA Hardware

断了今生、忘了曾经 提交于 2019-12-22 08:35:33
问题 ContextWin32::ContextWin32(WindowHandle parent, NLOpenGLSettings settings) : IPlatformContext(parent, settings) { int pf = 0; PIXELFORMATDESCRIPTOR pfd = {0}; OSVERSIONINFO osvi = {0}; osvi.dwOSVersionInfoSize = sizeof(OSVERSIONINFO); // Obtain HDC for this window. if (!(m_hdc = GetDC((HWND)parent))) { NLError("[ContextWin32] GetDC() failed."); throw NLException("GetDC() failed.", true); } // Create and set a pixel format for the window. pfd.nSize = sizeof(pfd); pfd.nVersion = 1; pfd.dwFlags

What instruction set does the Nvidia GeForce 6xx Series use?

安稳与你 提交于 2019-12-22 06:26:28
问题 Does the GeForce 6xx Series GPUS use RISC, CISC or VLIW style instructions? In one source, at http://www.motherboardpoint.com/risc-cisc-t241234.html someone said "GPUs are probably closer to VLIW than to RISC or CISC" . In another source, at http://en.wikipedia.org/wiki/Very_long_instruction_word#implementations it says "both Nvidia and AMD have since moved to RISC architectures in order to improve performance on non-graphics workload" 回答1: AFAIK, Nvidia does not publicly document it's

What instruction set does the Nvidia GeForce 6xx Series use?

家住魔仙堡 提交于 2019-12-22 06:26:27
问题 Does the GeForce 6xx Series GPUS use RISC, CISC or VLIW style instructions? In one source, at http://www.motherboardpoint.com/risc-cisc-t241234.html someone said "GPUs are probably closer to VLIW than to RISC or CISC" . In another source, at http://en.wikipedia.org/wiki/Very_long_instruction_word#implementations it says "both Nvidia and AMD have since moved to RISC architectures in order to improve performance on non-graphics workload" 回答1: AFAIK, Nvidia does not publicly document it's

Is stereoscopy (3D stereo) making a come back?

霸气de小男生 提交于 2019-12-21 23:03:53
问题 I'm working on a stereoscopy application in C++ and OpenGL (for medical image visualization). From what I understand, the technology was quite big news about 10 years ago but it seems to have died down since. Now, many companies seem to be investing in the technology... Including nVidia it would seem. Stereoscopy is also known as "3D Stereo", primarily by nVidia (I think). Does anyone see stereoscopy as a major technology in terms of how we visualize things? I'm talking in both a recreational

Can't “Attach to Process” to debug using Nsight in Visual Studio 2008

可紊 提交于 2019-12-21 20:57:34
问题 I'm trying to debug a cuda application using Nsight with Visual Studio 2008, so I opened the Attach to Process dialog. I set the Transport to be Nsight GPU Debugger. I set the Qualifier to the name of my machine (MONAD in this case). I see a list of processes in the Available Processes widget, but they are all greyed out, and if I click on my application, it remains greyed out and I cannot click the attach button. When I built the application I made sure to use the -G0 flag when compiling my

nvEncRegisterResource() fails with -23

夙愿已清 提交于 2019-12-21 20:54:29
问题 I've hit a complete brick wall in my attempt to use NVEnc to stream OpenGL frames as H264. I've been at this particular issue for close to 8 hours without any progress. The problem is the call to nvEncRegisterResource() , which invariably fails with code -23 (enum value NV_ENC_ERR_RESOURCE_REGISTER_FAILED, documented as "failed to register the resource" - thanks NVidia). I'm trying to follow a procedure outlined in this document from the University of Oslo (page 54, "OpenGL interop"), so I

How to turn off errors/warnings in Eclipse due to OpenCL/CUDA syntax?

时光总嘲笑我的痴心妄想 提交于 2019-12-21 19:24:23
问题 I am using Eclipse as an editor for OpenCL and I turned on syntax highlighting for *.cl files to behave like C++ code. It works great, but all my code is underlined as syntax errors. Is there a way that I can have my syntax highlighting and turn off the errors/warnings just for my *.cl files? 回答1: First, the Eclipse syntax highlighter is programmed to the grammar of C and C++, and not OpenCL, so it is unaware of the syntactic extensions of OpenCL, such as New keywords New data types I suggest

CUDA runtime version vs CUDA driver version - what's the difference?

喜欢而已 提交于 2019-12-21 06:58:29
问题 The CUDA Runtime API exposes the functions cudaRuntimeGetVersion() and cudaDriverGetVersion() (see detailed description here). I was sort of expecting the first one to give me "8.0" (for CUDA 8.0) and the second one to give me the same string as what I'd get from examining nVIDIA's GPU driver kernel module, e.g. modinfo nvidia | grep "^version:" | sed 's/^version: *//;' which on my system is 367.57 . Now, the first call gives me 8000 - fine, just a weird way to say 8.0 I guess; but the second