How kernel compiler c library work together

http://wiki.osdev.org/How_kernel,_compiler,_and_C_library_work_together

Static Library .a and Dynamic Library .so

http://www.ilkda.com/compile/Static_Versus_Dynamic.htm


Creating .so and .a in Unix
http://stackoverflow.com/questions/1648215/creating-so-and-a-in-unix

Difference between const & const volatile

http://stackoverflow.com/questions/4592762/difference-between-const-const-volatile

An object marked as const volatile will not be permitted to be changed by the code (an error will be raised due to the const qualifier) - at least through that particular name/pointer.

The volatile part of the qualifier means that the compiler cannot optimize or reorder access to the object.

In an embedded system, this is typically used to access hardware registers that can be read and are updated by the hardware, but make no sense to write to (or might be an error to write to).

unsigned int const volatile *status_reg; // assume these are assigned to point to the 
unsigned char const volatile *recv_reg;  //   correct hardware addresses


#define UART_CHAR_READY 0x00000001

int get_next_char()
{
    while ((*status_reg & UART_CHAR_READY) == 0) {
        // do nothing but spin
    }

    return *recv_reg;
}

If these pointers were not marked as being volatile, a couple problems might occur:

the while loop test might read the status register only once, since the compiler could assume that whatever it pointed to would never change (there's nothing in the while loop test or loop itself that could change it). If you entered the function when there was no character waiting in UART hardware, you might end up in an infinite loop that never stopped even when a character was received.
the read of the receive register could be moved by the compiler to before the while loop - again because there's nothing in the function that indicates that *recv_reg is changed by the loop, there's no reason it can't be read before entering the loop.


The volatile qualifiers ensures that these optimizations are not performed by the compiler.

debugging and optimization flags

http://software.intel.com/sites/products/documentation/doclib/stdxe/2013/composerxe/compiler/fortran-mac/GUID-1DB4628E-2171-47B1-83CB-1D26FF71C5A0.htm

Error: Unterminated character constant beginning at (1)

http://gcc.gnu.org/ml/fortran/2007-12/msg00212.html

Error: Unterminated character constant beginning at (1)
aaa.f:4.72:

           print *, 'Try one of "Skip", "Test", "Verbosity" or "Cleanup"
                                                                       1
Warning: Line truncated at (1)

Fixed-form Fortran has only 72 characters per line. What happens with
longer lines is implementation dependent. However, many
programmers/programs assume that everything after column 72 is ignored
(which gfortran does).

Solution: Fix the program by splitting the line or by using the 
-ffixed-line-length-n (n is a non-negative integer).

Does not name a type error in C++

http://stackoverflow.com/questions/2133250/does-not-name-a-type-error-in-c

using valgrind to check memory leak

http://cs.ecs.baylor.edu/~donahoo/tools/valgrind/

valgrind --tool=memcheck --leak-check=yes --show-reachable=yes --num-callers=20 --track-fds=yes ./test

g++ "nullptr" was not declared in this scope

http://stackoverflow.com/questions/11616539/g-nullptr-was-not-declared-in-this-scope

unrecognized command line option “-std=c++11” with g++

http://stackoverflow.com/questions/14674597/cc1plus-error-unrecognized-command-line-option-std-c11-with-g
In versions pre-G++ 4.7, you'll have to use -std=c++0x, for more recent versions you can use -std=c++11.

http://stackoverflow.com/questions/11616539/g-nullptr-was-not-declared-in-this-scope

AVR-GDB AVaRICE

http://winavr.sourceforge.net/AVR-GDB_and_AVaRICE_Guide.pdf

Interrupt and GCC Optimizer

http://web.engr.oregonstate.edu/~traylor/ece473/lectures/interrupts.pdf

C preprocessor #if defined

#if defined MACRO is precisely equivalent to #ifdef MACRO

NVCC Cubin vs PTX

http://stackoverflow.com/questions/7696230/nvidia-nvcc-and-cuda-cubin-vs-ptx

GPU: architecture and programming (NYU Course)

http://cs.nyu.edu/courses/spring12/CSCI-GA.3033-012/index.html

Contains some interesting links for GPU tools from webpage above
Multi2Sim Simulation Framework
http://www.multi2sim.org/

GPUocelot
http://code.google.com/p/gpuocelot/
Dynamic Compilation for PTX

Short CUDA tutorial of Colorado School of Mines
http://geco.mines.edu/tesla/cuda_tutorial_mio/index.html