public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: "Larry Hall \(Cygwin X\)" <reply-to-list-only-lh-x@cygwin.com> To: cygwin-xfree@cygwin.com Subject: Re: complains about the cygwin/gcc binaries Date: Thu, 27 Jan 2011 19:52:00 -0000 [thread overview] Message-ID: <4D41CCF7.5020609@cygwin.com> (raw) In-Reply-To: <4D41C957.2000202@purdue.edu> On 1/27/2011 2:36 PM, wxie wrote: > In the ROOT downloading website: > http://root.cern.ch/drupal/content/production-version-528 > It says: > "Note that the performance of cygwin/gcc binaries is currently very poor; we > only pro vide this build as an unsupported toy. We strongly recommend to use > the version above compiled with VC++. The ROOT team will not answer any > messages related to problems with the win32gcc version" > What's the reason of the poor performance. Is there any way to improve that? If you're posting something about Cygwin's gcc or Cygwin in general, the better list is cygwin at cygwin dot com. As for the statement above, I think you're better off asking the folks that are responsible for making the statement. There's obviously some overhead to the emulated environment that Cygwin provides but I can't say whether the statement is a general reference to this issue or to something more specific. -- Larry _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
next prev parent reply other threads:[~2011-01-27 19:52 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <4D41C8F2.8030509@purdue.edu> 2011-01-27 19:37 ` wxie 2011-01-27 19:52 ` Larry Hall (Cygwin X) [this message] 2011-01-27 20:07 ` marco atzeri 2011-01-27 22:22 Angelo Graziosi 2011-01-28 5:14 ` marco atzeri
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=4D41CCF7.5020609@cygwin.com \ --to=reply-to-list-only-lh-x@cygwin.com \ --cc=cygwin-xfree@cygwin.com \ /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).