Fix jit build break

[AndyAyersMS]

Two changes to codegencommon.cpp were merged in short order, and
git/github did not spot the merge conflict.

Fixes #32926.

[AndyAyersMS]

cc @kunalspathak @dotnet/jit-contrib @benaadams

[kunalspathak]

LGTM

[AndyAyersMS]

Will eagerly merge once a few builds pass.

[kunalspathak]

Probably I will add a note in Contributing.md to rebase to master and build locally to spot these kind of issues before merging the PR.

[AndyAyersMS]

(Building locally too, but it takes forever...)

[AndyAyersMS]

Needs a tweak...

[AndyAyersMS]

Think this is far enough along to merge.

[joperezr]

We have started seeing some build breaks on OSX that look like:

[ 67%] Building CXX object src/vm/CMakeFiles/cee_dac.dir/stackwalk.cpp.o
/Users/runner/runners/2.165.0/work/1/s/src/coreclr/src/jit/codegencommon.cpp:11307:31: error: too few arguments to function call, single argument 'compMethodID' was not specified
    m_StartEmitLocation.Print();
    ~~~~~~~~~~~~~~~~~~~~~~~~~ ^
/Users/runner/runners/2.165.0/work/1/s/src/coreclr/src/jit/emit.h:197:5: note: 'Print' declared here
    void Print(LONG compMethodID) const;
    ^
/Users/runner/runners/2.165.0/work/1/s/src/coreclr/src/jit/codegencommon.cpp:11311:33: error: too few arguments to function call, single argument 'compMethodID' was not specified
        m_EndEmitLocation.Print();
        ~~~~~~~~~~~~~~~~~~~~~~~ ^
/Users/runner/runners/2.165.0/work/1/s/src/coreclr/src/jit/emit.h:197:5: note: 'Print' declared here
    void Print(LONG compMethodID) const;
    ^
2 errors generated.
make[2]: *** [src/jit/standalone/CMakeFiles/clrjit.dir/__/codegencommon.cpp.o] Error 1
make[1]: *** [src/jit/standalone/CMakeFiles/clrjit.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....

@AndyAyersMS Would that be related to this PR?

cc: @layomia

[AndyAyersMS]

Yes, that error should be fixed by this PR.

[joperezr]

Yeah I thought this was causing that issue because we were seeing this in PR #32006 when re-running the checks about 1 hour ago, but looks like the reason for that is that it wasn't yet picking up this change, so we needed to close and then re-open the PR or to push a new commit to it in order to get the changes from here in order to fix that issue.