[m-rev.] for post-commit review: link_target_code.m

[Julien Fischer]

On Mon, 20 Jan 2025 at 00:42, Zoltan Somogyi <zoltan.somogyi at runbox.com> wrote:
>
> For review by anyone.

> Carve link_target_code.m out of compile_target_code.m.

...

> diff --git a/compiler/notes/compiler_design.html b/compiler/notes/compiler_design.html
> index 9a677f405..4e9e793e8 100644
> --- a/compiler/notes/compiler_design.html
> +++ b/compiler/notes/compiler_design.html
> @@ -311,8 +311,9 @@ Also used by mercury_compile.m to collect the value of DEFAULT_MCFLAGS,
>  which contains the auto-configured flags passed to the compiler.
>  </ul>
>
> -The build process also invokes routines in compile_target_code.m,
> -which is part of the backend_libs.m package (see below).
> +The build process also invokes routines
> +in compile_target_code.m and link_target_code.m,
> +which are part of the backend_libs.m package (see below).
>
>  <h2>Front end</h2>
>  <h3>1. Parsing</h3>
> @@ -2484,6 +2485,13 @@ It is used by both the LLDS and MLDS backends.
>  name_mangle.m defines predicates
>  for mangling names to forms acceptable as identifiers in target languages.
>  <li>
> +compile_target_code.m compiles
> +the code we generate in our various target languages,
> +converting C code to object files,
> +converting Java code to .jar files, and

compile_target_code will convert Java code into .class files.
(The new link_target_code module will handle the construction of .jar files.)

That looks fine otherwise.

Julien,