Boost C++ Libraries: Ticket #8700: multiprecision : Trying to cast to unsigned from cpp_int > 19 bits causes crash

John Maddock — Sun, 16 Jun 2013 08:09:12 GMT

Can you provide a self-contained test case please? Note that the beta for 1.54 is out now, so it might be easiest for you to test against that?

danq@… — Sun, 16 Jun 2013 21:26:35 GMT

I created a stripped-down test case, but it does not fail. No matter how large a count, the conversion works. Sigh...

I'm not sure how to go about integrating 1.54 into my toolset. I am using MinGW 10.2 distribution (a simple unzip and copy to destination folder type install).

One thought that just occurred to me is that the run-time stack probably increases as the cpp_int size increases (confirm?). Perhaps what is happening in my application code is the stack is heavily used and overflows somehow when I increases the bit size to 20 bits.

This might explain why the test case works. It has minimal stack requirements.

A side note (may be related):

This:

Bit_Reg i_value = i_addr >> i_field->bits.lsb ;

i_field->value = i_value.template convert_to <unsigned> () ;

Compiles while this:

i_field->value = static_cast <unsigned> (i_addr >> i_field->bits.lsb) ;

does not.

However, this:

Bit_Reg i_value = i_addr >> i_field->bits.lsb ;

i_field->value = static_cast <unsigned> (i_value) ;

works.

It seems that if I try to pass a temporary to the static_cast operator, the compiler complains.

I noticed this while trying to create a test case. Note: either method still fails when I reach 20 bits.

May or may not be related to the problem I am seeing.

Suggestions on how to install 1.54 beta into my (simple) Mingw environment?

Cheers!

Dan

John Maddock — Mon, 17 Jun 2013 08:02:45 GMT

Suggestions on how to install 1.54 beta into my (simple) Mingw environment?

Just unpack the zip and place it in your path - multiprecision is header only. If you need other Boost libs, the easiest way would be to temporarily rename boost/multiprecision in the 1.53 tree and then copy the version from 1.54 over to test.

BTW bit usage shouldn't effect stack usage in cpp_int. Have you run under gdb and/or looked up the error code to see if it's a stack overflow?

danq@… — Mon, 17 Jun 2013 12:35:12 GMT

News: Last night, I significantly increased the size of the run-time stack and the problem went away. Since you mentioned that cpp_int does not effect stack usage, I suspect that somewhere else in my code, the stack was getting loaded and by sheer chance, wound up clobbering my cpp_int variable.

I will play with GDB to see if I can pinpoint the cause.

I will also take a look at 1.54 and try to reproduce the problem with that version.

Thanks!

Dan

status changed; resolution set

John Maddock — Fri, 21 Jun 2013 16:09:42 GMT

status new → closed
resolution → invalid

Closing for now, please reopen if you confirm a Boost bug.