This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: target/10338: [3.3 regression?] [Cygwin -> tic4x | avr] cross target compilation error
- From: DJ Delorie <dj at redhat dot com>
- To: nobody at gcc dot gnu dot org
- Cc: gcc-prs at gcc dot gnu dot org,
- Date: 11 Apr 2003 02:16:01 -0000
- Subject: Re: target/10338: [3.3 regression?] [Cygwin -> tic4x | avr] cross target compilation error
- Reply-to: DJ Delorie <dj at redhat dot com>
The following reply was made to PR target/10338; it has been noted by GNATS.
From: DJ Delorie <dj at redhat dot com>
To: garen at wsu dot edu
Cc: gcc-gnats at gcc dot gnu dot org, Svein dot Seldal at solidas dot com, gcc-bugs at gcc dot gnu dot org,
nobody at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org
Subject: Re: target/10338: [3.3 regression?] [Cygwin -> tic4x | avr] cross target compilation error
Date: Thu, 10 Apr 2003 22:08:55 -0400
> So I don't think it's a regression. It seems to be present on all of the
> 3.2.x branches, so I'm guessing it's a Cygwin problem. I worked around it
> similarly by just not using __memcpy(), and instead memcpy() in the #else
> branch.
It looks like it's always been a bug, but until now there hasn't been
an OS that defined mempcpy (not memcpy) and not also __mempcpy, so we
just didn't trip over it.