PTX ADDC/SUBC PTX ADDC/SUBC. And, is there a bug tracking system?

I ran across this bug by accident, via a typo, in the PTX ADDC/SUBC instructions.

According to the PTX manual, ADDC is valid for 32 bits only, e.g., ADDC.U32, ADDC.S32, SUBC.U32, SUBC.S32. But, the PTXAS program also accepts other sizes, 16 and 64 bits. So, I think this is a (minor) bug in either the doc or PTXAS.

BTW, is there any way to search the Nvidia site for open bugs? The registered developer area has a “Current Bugs” search form, but it returns nothing. I suspect this may be because it only returns bugs that I submit, which would be very disappointing. (Or the code has no bugs ;). ) And, it does not seem to have a great way of selecting a subset either through “Division” or “Projects”, for ones associated with PTXAS. I don’t like making the forums a bug tracking system. But, until something better exists, I don’t see any good options.

[codebox] addc.u16 %s16_1, 0, 0; // Accepted, not documented.

addc.u32	%s32_1, 0, 0;

addc.u64	%s64_1, 0, 0;	// Acepted, not documented.

// addc.cc.u16 %s16_1, 0, 0; // Not accepted.

addc.cc.u32	%s32_1, 0, 0;

// addc.cc.u64 %s64_1, 0, 0; // Not accepted.

// add.cc.u16 %s16_1, 0, 0; // Not accepted.

add.cc.u32	%s32_1, 0, 0;

// add.cc.u64 %s64_1, 0, 0; // Not accepted.

subc.u16	%s16_1, 0, 0;	// Accepted, not documented.

subc.u32	%s32_1, 0, 0;

subc.u64	%s64_1, 0, 0;	// Accepted, not documented.

// subc.cc.u16 %s16_1, 0, 0; // Not accepted.

subc.cc.u32	%s32_1, 0, 0;

// subc.cc.u64 %s64_1, 0, 0; // Not accepted.

// sub.cc.u16 %s16_1, 0, 0; // Not accepted.

sub.cc.u32	%s32_1, 0, 0;

// sub.cc.u64 %s64_1, 0, 0; // Not accepted.

[/codebox]

I ran across this bug by accident, via a typo, in the PTX ADDC/SUBC instructions.

According to the PTX manual, ADDC is valid for 32 bits only, e.g., ADDC.U32, ADDC.S32, SUBC.U32, SUBC.S32. But, the PTXAS program also accepts other sizes, 16 and 64 bits. So, I think this is a (minor) bug in either the doc or PTXAS.

BTW, is there any way to search the Nvidia site for open bugs? The registered developer area has a “Current Bugs” search form, but it returns nothing. I suspect this may be because it only returns bugs that I submit, which would be very disappointing. (Or the code has no bugs ;). ) And, it does not seem to have a great way of selecting a subset either through “Division” or “Projects”, for ones associated with PTXAS. I don’t like making the forums a bug tracking system. But, until something better exists, I don’t see any good options.

[codebox] addc.u16 %s16_1, 0, 0; // Accepted, not documented.

addc.u32	%s32_1, 0, 0;

addc.u64	%s64_1, 0, 0;	// Acepted, not documented.

// addc.cc.u16 %s16_1, 0, 0; // Not accepted.

addc.cc.u32	%s32_1, 0, 0;

// addc.cc.u64 %s64_1, 0, 0; // Not accepted.

// add.cc.u16 %s16_1, 0, 0; // Not accepted.

add.cc.u32	%s32_1, 0, 0;

// add.cc.u64 %s64_1, 0, 0; // Not accepted.

subc.u16	%s16_1, 0, 0;	// Accepted, not documented.

subc.u32	%s32_1, 0, 0;

subc.u64	%s64_1, 0, 0;	// Accepted, not documented.

// subc.cc.u16 %s16_1, 0, 0; // Not accepted.

subc.cc.u32	%s32_1, 0, 0;

// subc.cc.u64 %s64_1, 0, 0; // Not accepted.

// sub.cc.u16 %s16_1, 0, 0; // Not accepted.

sub.cc.u32	%s32_1, 0, 0;

// sub.cc.u64 %s64_1, 0, 0; // Not accepted.

[/codebox]

Yep, there’s a bug tracking system…you just need to be a registered developer to sign in to it.

I actually spoke with some people from nVidia when I was out there for GTC a few weeks ago about the accuracy of ptxas’ verification algorithms. They’ve said they’re working on producing a new version of ptxas which will provide much stronger validation.

Yep, there’s a bug tracking system…you just need to be a registered developer to sign in to it.

I actually spoke with some people from nVidia when I was out there for GTC a few weeks ago about the accuracy of ptxas’ verification algorithms. They’ve said they’re working on producing a new version of ptxas which will provide much stronger validation.

I am a registered developer and logged in. Went to https://nvdeveloper.nvidia.com/login.asp, navigated via “Current Bugs” to form with title “Customer Problem Reports”, then select search with various qualifiers. No matter what Division, Projects, Status, etc. I input, the “search” button returns nothing “0 records found”. And, I get the same behavior no matter what browser I use (Chrome, Safari, Firefox, IE). How do I get this to work?

I am a registered developer and logged in. Went to https://nvdeveloper.nvidia.com/login.asp, navigated via “Current Bugs” to form with title “Customer Problem Reports”, then select search with various qualifiers. No matter what Division, Projects, Status, etc. I input, the “search” button returns nothing “0 records found”. And, I get the same behavior no matter what browser I use (Chrome, Safari, Firefox, IE). How do I get this to work?

You only see your own bugs as far as I know.
And yes, I also think the whole project, division and such distinction is a bit overkill as my co-worker in another division will have it’s own login…

You only see your own bugs as far as I know.
And yes, I also think the whole project, division and such distinction is a bit overkill as my co-worker in another division will have it’s own login…