[Profile] Handle binutils objdump RISC-V addresses

When regexing instructions for CFG targets, llvm-objdump outputs the
immediates for branches like:

    bne a6, s9, 0xf33e <_foo+0x7d0>

This we handle correctly with the current regex. However with binutils
there are no spaces nor 0x prefix:

    bne a6,s9,f33e <_foo+0x8d0>

This updates the regex to handle the binutils case by adding a specific
non-capturing group for other non-immediate operands, (?:[^\\s]+,\\s*)*

It also relaxes the immediate capture group to not require the 0x.
parseInt seems to handle the detection of the base for us.

Author: lukel97

lnt/server/ui/static/lnt_profile.js

@@ -103,9 +103,9 @@ InstructionSetParser.prototype = {
     RISCVJumpTargetRegexps: [
         // (regexp, noFallThru?)
         // branch conditional:
-        [new RegExp("^\\s*b[a-z]+\\s+.*(0x[0-9a-f]+)\\s+<.+>"), false],
+        [new RegExp("^\\s*b[a-z]+\\s+(?:[^\\s]+,\\s*)*([^\\s]+)\\s+<.+>"), false],
         // jumps:
-        [new RegExp("^\\s*(?:jal|j|call|tail)\\s+.*(0x[0-9a-f]+)\\s+<.+>"), true],
+        [new RegExp("^\\s*(?:jal|j|call|tail)\\s+(?:[^\\s]+,\\s*)*([^\\s]+)\\s+<.+>"), true],
         // indirect jumps:
         [new RegExp("^\\s*(?:jalr|jr|ret)"), true]
     ],