From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16406 invoked by alias); 11 Apr 2003 02:16:02 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 16378 invoked by uid 71); 11 Apr 2003 02:16:01 -0000 Date: Fri, 11 Apr 2003 02:16:00 -0000 Message-ID: <20030411021601.16377.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: DJ Delorie Subject: Re: target/10338: [3.3 regression?] [Cygwin -> tic4x | avr] cross target compilation error Reply-To: DJ Delorie X-SW-Source: 2003-04/txt/msg00484.txt.bz2 List-Id: The following reply was made to PR target/10338; it has been noted by GNATS. From: DJ Delorie To: garen@wsu.edu Cc: gcc-gnats@gcc.gnu.org, Svein.Seldal@solidas.com, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-prs@gcc.gnu.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.