More DG/UX Intel Build info

["Eric Raskin" <ehr at listworks dot com>]

I've looked closely at the test results from the testsuite after building on
DG/UX 4.20MU03 on the Intel platform.  I have the same tests failing here as
for the linux gcc platform [execute/980526-1.c, ieee/980619-1.c,
gcc.dg/980626-1.c, gcc.dg/clobbers.c, gcc.failure/940409-1.c], plus one
other set --  loop-2e.c, loop-2f.c, and loop-2g.c in gcc.c-torture/execute.
It seems this is a deficiency in the mmap() system call on DG/UX, in that
setting a MAP_FIXED memory map address overwrites memory somehow, resulting
in the exit() call failing.  In other words, the test itself succeeds and
exit() gets an error!

The fix I used was to change from a MAP_FIXED argument to letting the mmap()
call assign its own starting memory address.  These tests now succeed, and
the compiler tests as well here as it does on Linux.

Given this result and my previous post (DG/UX Intel Build problem) of this
morning, shall I post the patches made?  Is this considered "working well
enough" to be distributed?

TIA
----------------------------------------------------------------------------
----------------
Eric H. Raskin                                 Voice: 914-769-7100 x321
President, CSC Division                   Fax:    914-769-8070
The Listworks Corp.                         E-Mail: ehr@listworks.com
1 Campus Drive
Pleasantville, NY 10570