PTX code generation setting in create new cuda project nsight eclipse - eclipse

New laptop with GTX 1060. Just installed Ubuntu 16.04 and Cuda Toolkit 8.0.
I start with creating a new project:
Cuda C/C++ Project-> CUDA Runtime Projekt -> give name etc.
Then we get to the Generate PTX/GPU Code Setting. If i choose standard 3.5 and create project and run the generated example everything works as expected.
But if i choose only 6.0 on PTX and GPU code generation the example project will still run, but i will not have any cuda syntax highlights or auto completes in the file. Adding certain header files like cuda_runtime etc does not fix it.
I thought this setting is somewhat like "set compute capability to X.X" to get all the new cuda features with the higher version (like shfl, dynamic parallelism and so on). That's why i thought it should work like everything else if i select 6.0 instead of 3.5.
Am i missing something or am i just wrong about the expected behaviour?

Related

Standard Libraries are not recognized on RED (RobotFW 4.0)

I have a problem after making an update to run Robot Framework 4.0 with Python 3.7.9.
My OS is RedHat 7, I install a new RED, lates Robot (4.0) and the latest Python (3.7.9).
Everything was fine except when I launch RED (Eclipse RED - Robot Editor), Standard Libraries seems to not be recognized. On the Project explorer they appear:
BuiltIn (0)
Collections (0)
...
XML (0)
The strange thing is, when I right click on them to display the source code, RED open the source code correctly (but it does not work the documentation).
And Obviously my tests doesn't work, saying keyword from these libraries are not found.
During the installation I added the good paths to my bashrc so I don't think that the problem is here.
Does someone know what could be the problem?
RED does not support robotframework 4. See issue: https://github.com/nokia/RED/issues/413

Cannot disable CompactStrings Java 9 using Netbeans

I am trying to disable the CompactStrings feature of Java 9 using the VM option: -XX:-CompactStrings, but it does not work.
When I tried to debug my application, the COMPACT_STRINGS variable in String class is always true (with or without the VM option)
I have the latest version of Java 9: jdk-9+181
And the Netbeans IDE Build 201709070001
I tried various options to set the VM option and none of them works.
What I tried is:
setting the VM option in app.conf, setting it in project.properties, running netbeans by ./netbeans -XX:-CompactStrings, setting the JVM option in Project->Properties->Run->VM Options
Is this a bug in Netbeans? Or am I doing something wrong?
I tried to reproduce your problem using a trivial "Hello World" Java application. However, toggling the CompactStrings feature in the project properties settings worked fine for me, and caused COMPACT_STRINGS to be set appropriately, so this is not a bug in NetBeans.
Although I am using the same version of Java (181) as you, I have a more recent Dev Build of NetBeans (Build 201709220002), and there are several discrepancies between my project properties screen and yours. For example, mine shows the Runtime Platform field but yours does not:
Something else to check is that you really do have the environment you expect. I find it easy to mess things up when multiple versions of Java and Netbeans are installed.
This is what I see when I do Help -> About:
If your environment looks fine then I can only suggest that you download the latest DEV Build of NetBeans and try again.

using libGDX/gradle with Netbeans

I want to learn to use libGDX to create android apps/games.
I used the installer from the libGDX website to create a new project, installed gradle (on windows10) and am able to build/run my project through command line. (tested desktop version and apk via bluestacks, both work nice)
My problem is now, that Netbeans cannot display my code correctly. It says cannot access java.lang at the first line, and things like cannot find symbol, package * does not exist or Override is not an annotation type at the other errors.
I mean, it works somehow, but it's not nice development like that. How can i fix those errors?

Error while Debugging using Eclipse for DS-5

I am using DS5 evaluation version. I created a simple hello world C project in eclipse for DS5. Project type chosen while creating the project is Bare Metal executable->Empty project. Tool chains ARM Compiler 5 was selected. I complied the code and generated the axf file. When i right click on the axf file and select debug as->debug configurations->Connection tab->ARM FVP VE_Cortex_A7x1->Bare Metal Debug->Debug Cortex-A7 and click on debug I am facing the error as in the image.
Please let me know how to resolve the same.
The reason you're seeing that error is that the evaluation version of DS-5 Professional Edition gives you access to the Cortex-A8 and Cortex-A9 FVPs, not the Cortex-A7 one.
Extra FVPs need to be purchased separately from ARM.

How to set up Eclipse for FPGA design in VHDL and Verilog)?

I am new with Eclipse, I have used it for SW development and in Altra environment for Nios processor. But now, I have a pretty large project that I have to manage and I would like to use Eclipse to have all the files in the system to make it easier to manage and update.
The project has multiple directories for various IPs and has multiple targets for ASCI, Xilinx and Altera FPGAs. In a near future the project will support both NIOS, Microblaze and ARM processors and I would really like to keep the whole project in one Eclipse project file if possible. I have tried several different options, but nothing seems to work properly.
I am looking for some freeware and not commercial programs like Sigasi.
Thanks in advance,
Farhad
This is an update to let others know about my progress.
Well, I finally managed to get it to work.
I installed the latest version of Eclipse on my PC
Installed version 6 of Java (the only one I could get to work)
Installed the latest version of the VEditor into Eclipse.
Mounted the Linux project directory as my P disk on PC
created a new project in Eclipse and linked it to the one on the P drive.
It took some time to figure this out, but it now works perfectly.
These are the ones I know of:
Veditor (beta) - http://sourceforge.net/projects/veditor/
sigasi free - http://www.sigasi.com/sigasi-starter-edition
signs (no longer in development) - http://sourceforge.net/projects/signs/
zamiaCAD (replacement of signs) - http://zamiacad.sourceforge.net/web/