[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Viuavm-commits] [SCM] Viua VM branch devel updated. v0.9.0-2330-g3e53ab

From: git
Subject: [Viuavm-commits] [SCM] Viua VM branch devel updated. v0.9.0-2330-g3e53ab9
Date: Tue, 8 Jan 2019 19:39:41 +0100 (CET)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Viua VM".

The branch, devel has been updated
       via  3e53ab99214e512982b857aed6c8e042b854d3cf (commit)
       via  03d96d429d729d4a3c104a2a0f3afa9a732162fd (commit)
       via  f351ced962216cb2f8cc4a28f40eb1ade553e36a (commit)
       via  752f9a705c39dd1b0030d7cd92fa33ea9bdb026f (commit)
      from  8558b99a81705a530b1f697a9fe298133196f015 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 3e53ab99214e512982b857aed6c8e042b854d3cf
Author: Marek Marecki <address@hidden>
Date:   Tue Jan 8 19:39:12 2019 +0100

    Update changelog

commit 03d96d429d729d4a3c104a2a0f3afa9a732162fd
Author: Marek Marecki <address@hidden>
Date:   Tue Jan 8 19:37:47 2019 +0100

    Use more auto
    There is no reason to repeat ourselves in code if the compiler can
    deduce the types.

commit f351ced962216cb2f8cc4a28f40eb1ade553e36a
Author: Marek Marecki <address@hidden>
Date:   Tue Jan 8 19:35:17 2019 +0100

    Fix: allow static linking of more than one module in a single run
    This bug was triggered by the compiler project I do as part of getting
    my engineer's degree. It's incredibly weird that I have never before
    tried to link more than one module in a single invocation of the
    assembler... Well, it's not the first time I encounter a weird bug
    during the development of the VM. Lucky me that fixing this one took
    roughly 10 minutes without first hunting for it for several days.

commit 752f9a705c39dd1b0030d7cd92fa33ea9bdb026f
Author: Marek Marecki <address@hidden>
Date:   Tue Jan 8 19:31:13 2019 +0100

    Fix: stop analysing a control flow path after encountering a tail call
    Tail call causes the control flow to be transferred to a far away land
    that we have no knowledge of (similarly to what a RETURN or THROW
    instructions do). It is not only pointless but also incorrect to
    continue analysing the current control flow path as it is broken at the
    point of the tail call (as the currently executing frame is replaced).


Summary of changes:
 Changelog.markdown                                        |  4 ++++
 include/viua/version.h                                    |  2 +-
 src/assembler/frontend/static_analyser/register_usage.cpp | 12 +++++++++++-
 src/front/asm/generate.cpp                                | 14 +++++++++-----
 4 files changed, 25 insertions(+), 7 deletions(-)

Viua VM

reply via email to

[Prev in Thread] Current Thread [Next in Thread]