[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 294695] New: Wish for CUDA source code support, such as header switching, syntax highlighting,
From:       Anonymous <robohead44 () yahoo ! com>
Date:       2012-02-23 15:14:19
Message-ID: bug-294695-40295 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=294695

           Summary: Wish for CUDA source code support, such as header
                    switching, syntax highlighting, and basic language
                    support.
           Product: kdevelop
           Version: unspecified
          Platform: Ubuntu Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs@kdevelop.org
        ReportedBy: robohead44@yahoo.com


Version:           unspecified (using KDE 4.7.4) 
OS:                Linux

NVIDIA CUDA is becoming more and more common for GPU computing (and seems to
become the de-facto choice over OpenCL, as many closed and open-sources
projects tend to gravitate toward it (see e.g. OpenCV's recent support for
CUDA)). Currently kdevelop does not recognize CUDA files, but it would be nice
if it did.
Its syntax is essentially an extension to C++, so parsing should not be that
difficult of a problem.

I am wishing for 4 things, in ascending order of difficulty:

1) Recognition of .cuh and .cu files as CUDA files, and automatic selection of
the correct syntax highlighting. (This might actually be a request for
katepart, I am not sure). Currently, this association can be manually worked
around in the "Configure Editor"->"Open/Save"->"Modes &
Filetypes"->"Sources/C++"->adding .cu and .cuh to the file extensions. Of
course that's a hack and doesn't give "true" CUDA syntax support, as there
currenly is not "Sources/CUDA". But at least we get C++ highlighting.
2) Kdevelop understanding the relationship between .cu / .cuh, so that "Switch
Definition/Declaration" works to switch between headers (.cuh / .h) and
implementation files (.cu).
3) Kdevelop having "*.cu,*.cuh" extensions be automatically a part in the "Find
in Files" feature.
4) Correct parsing of CUDA code. This mostly works already if I manually
associate .cu files with the C++ language in the kate options, but of course
some of the CUDA-specific syntax, such as kernel_call<<<blocks, threads>>> is
not parsed or understood correctly. Also commands, such as cudaMalloc and
cudaFree are currently not resolved correctly.


Reproducible: Always

Steps to Reproduce:
Open some CUDA code (a .cu and .cuh file) in kdevelop. Look at editor.


Actual Results:  
- There is no syntax highlighting.
- Trying to use the switch feature between CUDA definition/declaration does not
work.
- Find in Files, does not search .cu or .cuh files.
- When manually associating CUDA .cu and .cuh extensions with C++ parser then
syntax highlighting and code parsing is incomplete, as the parser is unaware of
CUDA syntax.

Expected Results:  
- CUDA syntax is highlighted correctly
- The parser understands CUDA syntax extensions, such as
kernel_call<<<...,...>>>
- Switching between definition/declaration works for CUDA code even when file
extensions are .cuh or .cu.
- Find in Files will include .cu and .cuh files.


For CUDA language information, see this page:

http://developer.nvidia.com/nvidia-gpu-computing-documentation

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs
[prev in list] [next in list] [prev in thread] [next in thread]