public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Svein E. Seldal" <Svein.Seldal@solidas.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/10338: [3.3 regression?] [Cygwin -> tic4x | avr] cross target compilation error Date: Fri, 11 Apr 2003 02:06:00 -0000 [thread overview] Message-ID: <20030411020601.6986.qmail@sources.redhat.com> (raw) 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
next reply other threads:[~2003-04-11 2:06 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-11 2:06 Svein E. Seldal [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-25 15:15 ghazi 2003-04-11 2:16 DJ Delorie 2003-04-11 1:36 Garen
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20030411020601.6986.qmail@sources.redhat.com \ --to=svein.seldal@solidas.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).