mirror of
https://github.com/Mercury-Language/mercury.git
synced 2026-04-20 11:54:02 +00:00
2bd7c5ee3e
tests/hard_coded/*.m:
Rename modules as mentioned above.
In a few cases, where the main module's name itself had a suffix,
such as "_mod_a" or "_main", remove that suffix. This entails
renaming the .exp file as well. (In some cases, this meant that
the name of a helper module was "taken over" by the main module
of the test case.)
Update all references to the moved modules.
General updates to programming style, such as
- replacing DCG notation with state var notation
- replacing (C->T;E) with (if C then T else E)
- moving pred/func declarations to just before their code
- replacing io.write/io.nl sequences with io.write_line
- replacing io.print/io.nl sequences with io.print_line
- fixing too-long lines
- fixing grammar errors in comments
tests/hard_coded/Mmakefile:
tests/hard_coded/Mercury.options:
Update all references to the moved modules.
Enable the constant_prop_int test case. The fact that it wasn't enabled
before is probably an accident. (When constant_prop_int.m was created,
the test case was added to a list in the Mmakefile, but that list
was later removed due to never being referenced.)
tests/hard_coded/constant_prop_int.{m,exp}:
Delete the calls to shift operations with negative shift amounts,
since we have added a compile-time error for these since the test
was originally created.
38 lines
1.3 KiB
Mathematica
38 lines
1.3 KiB
Mathematica
%---------------------------------------------------------------------------%
|
|
% vim: ts=4 sw=4 et ft=mercury
|
|
%---------------------------------------------------------------------------%
|
|
%
|
|
% Versions of the compiler up to April 19, 2006 had a bug that caused this
|
|
% program to crash. The bug was that when frameopt wanted to find out whether
|
|
% a block of instructions referred to stack variables, it did not look past
|
|
% pragma_c_code LLDS instructions. As a result, the generated code included
|
|
% a (redundant) assignment to a stack variable in a section of code that,
|
|
% after frameopt, did not have a stack frame anymore. It therefore overwrote
|
|
% part of its caller's stack frame, which caused a crash.
|
|
%
|
|
% The bug showed up in YesLogic's Prince, and was isolated to this test case
|
|
% by Michael Day. The bug actually occurred when optimizing get_max_width in
|
|
% prince_frameopt_css.style.m.
|
|
|
|
:- module prince_frameopt.
|
|
|
|
:- interface.
|
|
|
|
:- import_module io.
|
|
|
|
:- pred main(io, io).
|
|
:- mode main(di, uo) is det.
|
|
|
|
:- implementation.
|
|
|
|
:- import_module string.
|
|
|
|
:- import_module prince_frameopt_helper_1.
|
|
:- import_module prince_frameopt_helper_1.prince_frameopt_helper_2.
|
|
|
|
main(!IO) :-
|
|
io.write_string("About to crash\n", !IO),
|
|
PRules = new_prules,
|
|
io.write_line(PRules, !IO),
|
|
io.write_string("Done\n", !IO).
|