From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7226 invoked by alias); 11 Apr 2003 02:06:12 -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 6987 invoked by uid 71); 11 Apr 2003 02:06:01 -0000 Date: Fri, 11 Apr 2003 02:06:00 -0000 Message-ID: <20030411020601.6986.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: "Svein E. Seldal" Subject: Re: target/10338: [3.3 regression?] [Cygwin -> tic4x | avr] cross target compilation error Reply-To: "Svein E. Seldal" X-SW-Source: 2003-04/txt/msg00483.txt.bz2 List-Id: The following reply was made to PR target/10338; it has been noted by GNATS. From: "Svein E. Seldal" To: Garen Cc: gcc-gnats@gcc.gnu.org, 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: Fri, 11 Apr 2003 03:57:02 +0200 Garen wrote: > I ran into the same problem here (PR10198): > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10198 > > 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. > Yes its the same bug... Well it depend on how you define regression. It seems like this is a Cygwin regression and not a gcc one, because it *did* work on the gcc-3.3-branch at 20030315, and now it dont (using that date's snapshot). The same applies to the 3.2.x branches. But my point is, that if this is caused by a Cygwin thing, what approach should we take to fix it? Fix Cygwin or fix gcc? Svein