Ad
  • Default User Avatar

    I like your sete. Good thinking!

  • Default User Avatar

    I found my mistake. Keep an eye on your register sizes. I started with 8bit regs, and only switched to 64bit regs when I saw the random long str test. I simply forgor to change 1 line to get a 64bit value and not only 8bit.

  • Default User Avatar

    This comment is hidden because it contains spoiler information about the solution

  • Default User Avatar

    NASM. My code solves all BasicTests and RandomTests. TestsStringsUpTo40kLenForPerfomanceAssesment then fails on the first tested string pair. It is not a time out, it says "Incorrect answer for". Any ideas for potential pit falls when handling these very long strings?

  • Default User Avatar

    NASM translation Please have a look at it.

  • Default User Avatar

    In addition to monadius note. I tried malloc before and I got a sigsegv. I doubted malloc at that point, but it was a special case that caused this crash. So for anyone else struggling, watch out for special test cases. There is a sneaky one.

  • Default User Avatar

    Thanks for the clarification. For some reason I expected that it is intended to use the RDI-pointer not only for the length but also for the result arr. Have a nice day.

  • Default User Avatar

    NOTE: Extra spaces before or after the code have no meaning and should be ignored.

  • Default User Avatar

    Another thanks for your explanation and your provided link. Have a nice day.

  • Default User Avatar
        ______
       /  ___ \
      |  / ,.\ |O    O
      | |  \d/ | \__/
      |__\_____/-(..)
    _/_____________/  
    SNAILICIOUS KATA
    
  • Default User Avatar

    NASM question. In which format is the result expected? So far I figured out, that I return a pointer, which I received in [rdi], and I put the length of my out arr into [rdi+0], then I can not use [rdi+8]. All my numbers are stored in [rdi+n*8+8]. As last part I move rdi into rax, but with an offset. I can not set the offset to 16, this just crashes. Offset = 0, and my result list is off by two positions. Offset = 8, and my result list is off by one position. Offset = 24 and my result is off by one but in the other direction.

  • Default User Avatar

    This comment is hidden because it contains spoiler information about the solution

  • Default User Avatar

    This comment is hidden because it contains spoiler information about the solution

  • Default User Avatar

    This kata is about learning and using string operations. This is the learning goal. Why do you need these string operations? Imagine you write a small programm that reads an input number and squares the number. In many languages, this includes Python, you will receive a string as an input from the user. So it's important for you to know what to do if you receive a string while wanting to do some math with the input.

  • Default User Avatar

    Are the NASM hidden tests working as intended? The visible tests already test 6,4 with result 23 and I can solve all the visible tests. When attempting the hidden tests, I can print that both numbers are also 6,4 but this time they expect a 1919,

  • Loading more items...