public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: target/10338: [3.3 regression?] [Cygwin -> tic4x | avr] cross target compilation error
@ 2003-04-25 15:15 ghazi
  0 siblings, 0 replies; 4+ messages in thread
From: ghazi @ 2003-04-25 15:15 UTC (permalink / raw)
  To: Svein.Seldal, gcc-bugs, gcc-prs, nobody

Synopsis: [3.3 regression?] [Cygwin -> tic4x | avr] cross target compilation error

State-Changed-From-To: open->closed
State-Changed-By: ghazi
State-Changed-When: Fri Apr 25 15:15:07 2003
State-Changed-Why:
    Fixed in 3.3, too late for 3.2.3.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10338


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: target/10338: [3.3 regression?] [Cygwin -> tic4x | avr] cross target compilation error
@ 2003-04-11  2:16 DJ Delorie
  0 siblings, 0 replies; 4+ messages in thread
From: DJ Delorie @ 2003-04-11  2:16 UTC (permalink / raw)
  To: nobody; +Cc: gcc-prs

The following reply was made to PR target/10338; it has been noted by GNATS.

From: DJ Delorie <dj@redhat.com>
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.


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: target/10338: [3.3 regression?] [Cygwin -> tic4x | avr] cross target compilation error
@ 2003-04-11  2:06 Svein E. Seldal
  0 siblings, 0 replies; 4+ messages in thread
From: Svein E. Seldal @ 2003-04-11  2:06 UTC (permalink / raw)
  To: nobody; +Cc: gcc-prs

The following reply was made to PR target/10338; it has been noted by GNATS.

From: "Svein E. Seldal" <Svein.Seldal@solidas.com>
To: Garen <garen@wsu.edu>
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
 


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: target/10338: [3.3 regression?] [Cygwin -> tic4x | avr] cross target compilation error
@ 2003-04-11  1:36 Garen
  0 siblings, 0 replies; 4+ messages in thread
From: Garen @ 2003-04-11  1:36 UTC (permalink / raw)
  To: nobody; +Cc: gcc-prs

The following reply was made to PR target/10338; it has been noted by GNATS.

From: Garen <garen@wsu.edu>
To: gcc-gnats@gcc.gnu.org, Svein.Seldal@solidas.com,
	gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-prs@gcc.gnu.org
Cc:  
Subject: Re: target/10338: [3.3 regression?] [Cygwin -> tic4x | avr] cross target compilation error
Date: Thu, 10 Apr 2003 18:12:59 -0700

 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.
 
 


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2003-04-25 15:15 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-04-25 15:15 target/10338: [3.3 regression?] [Cygwin -> tic4x | avr] cross target compilation error ghazi
  -- strict thread matches above, loose matches on Subject: below --
2003-04-11  2:16 DJ Delorie
2003-04-11  2:06 Svein E. Seldal
2003-04-11  1:36 Garen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).