f16e64c087
The fix is in two parts.
compiler/disj_gen.m:
The first is fixing a bug I introduced recently while fixing
github issue #90. The fix involved flushing resume vars to the stack
*before* executing the code of a non-last disjunct, but the state of
the code generator while generating the code of that disjunct needs
to reflect this having been done. The earlier change did not do this,
but this one does.
library/exception.m:
The second part is some needed declarations of entry labels
were not visible when compiling exception.c. Give exception.m,
and hence exception.c, access to the declarations of those labels
by #including the files containing the declarations, and ...
library/profiling_builtin.m:
... include two such declarations in the .mh file of this module
for use by exception.m.
tests/EXPECT_FAIL_TESTS.asm_fast.gc.profdeep:
Expect the setenv test case to fail in deep profiling grades, since
(in the absence of working tail recursion while deep profiling)
its million-calls-deep recursion to construct a million cons cells
allocates *much* more memory per recursive call than in other grades,
and thus running out of memory is the expected result.
Conflicts:
compiler/disj_gen.m
Mercury
Mercury is a logic/functional programming language which combines the clarity and the expressiveness of declarative programming with advanced static analysis and error detection features.
More information is available on the website's about pages, in other README files in the source code repository, and in the documentation.
README files
The Mercury compiler has a number of different backends and works on different operating systems. Specific information is contained in individual README files:
-
Bootstrapping discusses how to get Mercury installed.
This is important as the Mercury compiler is written in Mercury.
-
C Low-level backend
This backend works well with GCC but also works with:
-
High-level backend targets
-
Platforms
-
Cross compilation
Other information
See the current release notes for the latest stable release. The history file is relevant if you want to find out more about the past development of Mercury. News lists any current or future enhancements (but this isn't always up-to-date). The limitations file lists a number of ways in which the Mercury implementation does not yet meet its goals.
Information for developers
If you are considering contributing to the Mercury project the website contains some documents that may be helpful. These include a document about contributions in general and specific information about contributing such as coding styles.
Contact
See our contact page.