This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Sequent Dynix 4.4.2 problems with g++ compiler (w/fix suggested)
- To: bug-gnu-gcc at gnu dot org, fubar at sequent dot com, rfg at monkeys dot com
- Subject: Re: Sequent Dynix 4.4.2 problems with g++ compiler (w/fix suggested)
- From: Mike Stump <mrs at windriver dot com>
- Date: Tue, 25 Jan 2000 12:04:48 -0800 (PST)
> To: bug-gnu-gcc@gnu.org, Jay Vosburgh <fubar@sequent.com>
> Date: Mon, 24 Jan 2000 19:19:19 -0800
> From: "Ronald F. Guilmette" <rfg@monkeys.com>
> Unfortunately, whoever implemented the C library bcopy() function
> for Dynix 4.4.2 didn't look closely enough at the original bcopy()
> man page from BSD UNIX, and it appears the Dynix 4.4.2 bcopy() _does
> not_ properly handle the case where the input and output regions
> overlap.
In that case, I would say arrange for libiberty to include bcopy
through the normal magic, and then gcc will just use it. Maybe an
autoconf test that checks bcopy on the system to see if it `really'
does work, and it it doesn't, pull it in.