UInt256 returns wrong value

sora · June 11, 2025, 9:36pm

I think we simply didn’t update SIMD.write_to after introducing the larger integer types. Change 64 to max(64, dtype.bitwidth()) and it works.

github.com/modular/modular

mojo/stdlib/stdlib/builtin/format_int.mojo

e6523da95


      
                  ptr=zero_buf.unsafe_ptr(), length=1
              )
              writer.write(zero)
          
              return None
          
          # Create a buffer to store the formatted value
          
          # Stack allocate enough bytes to store any formatted 64-bit integer
          # TODO: use a dynamic size when #2194 is resolved
          alias CAPACITY: Int = 64 + 1  # +1 for storing NUL terminator.
          
          var buf = InlineArray[UInt8, CAPACITY](uninitialized=True)
          
          # Start the buf pointer at the end. We will write the least-significant
          # digits later in the buffer, and then decrement the pointer to move
          # earlier in the buffer as we write the more-significant digits.
          var offset = CAPACITY - 1
          
          buf.unsafe_ptr().offset(offset).init_pointee_copy(
              0

Topic		Replies	Views
Failed to use Python hex() function in Mojo Mojo	1	50	June 4, 2025
Failed to convert hex string to UInt256 Mojo	2	39	June 5, 2025
Pow() function returns incorrect value Mojo	4	84	June 25, 2025
How to convert for example Int8 to Int Mojo debugging , 24_6	4	85	March 3, 2025
`pack_bits` inside of vectorize fails constraint check Mojo 25_3	10	94	May 7, 2025

UInt256 returns wrong value

Related topics