information gets into log files if output is redirected.
* Add 1000 to ExitStatus if TerminateSentCount is > 0
to allow better discrimination between inferior exitcode and
stop due to Terminate use.
git-svn-id: trunk@34326 -
Fix infinite loop problem that appear on gcc112 linux machine using GNU make 4.0.
* Never put destination directory in the dependency list, as it gets modified when
the target file is created and led to infinite recursion.
We cannot use $(MKDIRTREE) unconditionally as this generates make error
at least on Windows OS.
Instead, create an explicit target for $(TEST_OUTPUTDIR), and add a:
$(MAKE) $dir
line on gparmake, createlst and $(MAKEINC) targets explicitly.
git-svn-id: trunk@34325 -
* Never put destination directory in the dependency list, as it gets modified when
the target file is created and led to infinite recursion.
We cannot use $(MKDIRTREE) unconditionally as this generates make error
at least on Windows OS.
Instead, create an explicit target for $(TEST_OUTPUTDIR), and add a:
$(MAKE) $dir
line on gparmake, createlst and $(MAKEINC) targets explicitly.
git-svn-id: trunk@34324 -
are not compiled at the same time (because otherwise the compiler may
trip over itself in case it performs linking via an external script or
using a response file)
git-svn-id: trunk@34322 -
* Never modify the first half of LowerCaseTable:
even if 'A' is the upper form of 'a' with an accent ('…'),
that doesn't mean that the lowercase form of 'A' should be
'a' with the accent ('…') instead of plain 'a'.
git-svn-id: trunk@34321 -
The problem was in the source of random related functions,
which are used in this test by several thread in parallel,
while this code is known and advertised as non-thread safe.
The access by multiple threads led to multiple increments of the
mt_index static variable, which was then never reset to zero and
led to all successive calls to random function to return zero.
This fix simply insures that the mt_state array is never
accessed past its end, and that mt_index is reset correctly even
if multiple increments do happen.
It does not make the random function thread-safe.
* Use local variable l_index to avoid accessing mt_state array past last element.
* Change mt_index=MTWIST_N+1 into l_index>=MTWIST_N+1
to insure that mt_init will be called again if index is past end.
git-svn-id: trunk@34320 -
in exit nodes, because the wrapping code added in
tnodeutils.wrap_proc_body() gets inserted before the exit label to which
the exit node jumps
git-svn-id: trunk@34305 -
alignment of the resultdef rather than to 0 (required for llvm, and
cleaner since then the code generator knows the actual alignment)
git-svn-id: trunk@34296 -
modulo7, mantis #30381)
o check for array elements of size 0 does not make sense after we've
established it's an array of floats
o since the recursive call to is_hfa_internal() already checks for
floats, we don't have to do it before calling it again for the
elements of an array
o set the result to "true" if the array is small enough to be a HFA
git-svn-id: trunk@34293 -
release the source location in case it was also a temp. Reason: we
don't increase reference counts when assigning to a ti_const (they are
like const parameters), so the original value must stay alive until
the ti_const temp is freed
o free the original data in the ttempdelete node for the ti_const temp
o don't increase reference counts when assigning composite types to
ti_const temps either
git-svn-id: trunk@34287 -
parameters into temps in case it's required for correctness (so we
can easily "early exit" on failure from the latter) (still no
functional changes)
git-svn-id: trunk@34284 -
