C++: Add dmd::printInstantiationTrace to compiler interface

[ibuclaw]

Because printInstantiationTrace is an extern(D) method.

---

So with the following compiler glue code for RTTI.

  if (!global.params.useTypeInfo)
    {
      if (!sc || !sc->ctfe ())
        {
          error_at (loc, "`object.TypeInfo` cannot be used with `-fno-rtti`");

          if (sc && sc->tinst)
            dmd::printInstantiationTrace (sc->tinst);

          global.errors++;
        }
    }

We get stack traces that link back to the originating code along with the error within the druntime template.

core/internal/array/utils.d:154:41: error: ‘object.TypeInfo’ cannot be used with ‘-fno-rtti’
core/internal/array/construction.d:388:24: note: instantiated from here: ‘__arrayAlloc!(Bucket!(int, int))’
core/internal/array/construction.d:402:18: note: instantiated from here: ‘_d_newarrayU!(Bucket!(int, int))’
core/internal/newaa.d:363:16: note: instantiated from here: ‘_d_newarrayT!(Bucket!(int, int))’
core/internal/newaa.d:44:5: note: instantiated from here: ‘Impl!(int, int)’
core/internal/newaa.d:83:25: note: instantiated from here: ‘AA!(int, int)’
core/internal/newaa.d:611:27: note: instantiated from here: ‘_toAA!(int, int)’
testsuite/gdc.dg/rtti1.d:7:16: note: instantiated from here: ‘_d_aaIn!(int[int], int, int, int)’

[dlang-bot]

Thanks for your pull request, @ibuclaw!

Bugzilla references

Your PR doesn't reference any Bugzilla issue.

If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog.

Testing this PR locally

If you don't have a local development environment setup, you can use Digger to test this PR:

dub run digger -- build "master + dmd#22139"