What steps will reproduce the problem? 1. Try to compile something like this
.entry foo
{
{
.reg .u32 some_temp_reg;
add some_temp_reg, some_temp_reg, 1;
}
} What is the expected output? What do you see instead? Ocelot's PTX parser should define some_temp_reg only until the end of the
curly brace. It should also allow multiple levels of nesting.
jwang323
commented
9 years ago
From gregory....@gatech.edu on September 28, 2011 19:39:00
What steps will reproduce the problem? 1. Try to compile something like this
.entry foo { { .reg .u32 some_temp_reg; add some_temp_reg, some_temp_reg, 1; } } What is the expected output? What do you see instead? Ocelot's PTX parser should define some_temp_reg only until the end of the curly brace. It should also allow multiple levels of nesting.
Original issue: http://code.google.com/p/gpuocelot/issues/detail?id=59