Question: I want this button's image use the image stored in database (image path)...

```
        private void button15_Click(object sender, EventArgs e)
        {
            string a = button11.Text;
            string connString = "Server=Localhost;Database=test;Uid=*****;password=*****;";
            MySqlConnection conn = new MySqlConnection(connString);
            MySqlCommand command = conn.CreateCommand();
            command.CommandText = ("Select link from testtable where ID=" + a);

            try
            {
                conn.Open();
            }
            catch (Exception ex)
            {
                //button11.Image = ex.ToString();
            }

            MySqlDataReader reader = command.ExecuteReader();
            while (reader.Read())
            {
                button11.Image = reader["path"].ToString();                    
            }
        } 

```

I think the error lies in `"reader["path"].ToString();"` but I don't know what syntax to use.

Answer: 
The CUDA Toolkit [Release Notes](http://docs.nvidia.com/cuda/cuda-toolkit-release-notes/index.html) list the supported platforms and compilers.
Well I think it's the other way around. The thing is, there is a driver called `nvcc`. it generates device code and host code and sends the host code to a compiler. It should be a C compiler and it should be in the executable path. (EDIT: and it should be gcc on Linux and cl on Windows and I think I should ignore mac as the release note did(?))

nvcc Compiler Info reads:

> 
> A general purpose C compiler is needed by nvcc in the following
> situations:
> 
> 
> 1. During non-CUDA phases (except the run phase), because these phases will be forwarded by nvcc to this compiler
> 2. During CUDA phases, for several preprocessing stages (see also 0). On Linux platforms, the compiler is assumed to be ‘gcc’, or ‘g++’ for linking. On Windows platforms, the compiler is assumed to be ‘cl’. The
> compiler executables are expected to be in the current executable
> search path, unless option -compiler-bin-dir is specified, in which
> case the value of this option must be the name of the directory in
> which these compiler executables reside.
> 
> 
> 

And please don't talk like that about compilers. Your code is in a way that works better with Dev-C++. What is generated is an assembly code. I don't say that they don't make any difference, but maybe 4 to 5%, not 100%.

And absolutely definitely don't blame the compiler for your slow program. It is definitely because of inefficient memory access and incorrect use of different types of memory.