public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: marco atzeri <marco.atzeri@gmail.com>
To: cygwin-xfree@cygwin.com
Subject: Re: complains about the cygwin/gcc binaries
Date: Thu, 27 Jan 2011 20:07:00 -0000	[thread overview]
Message-ID: <AANLkTimZMLAxHGLvk4ND0RVDo6YiDRd4mDFL7H4twF3F@mail.gmail.com> (raw)
In-Reply-To: <4D41C957.2000202@purdue.edu>

On Thu, Jan 27, 2011 at 8:36 PM,  wrote:
> In the ROOT downloading website:
> http://root.cern.ch/drupal/content/production-versio
> n-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?
>
> Thanks
> --Wei

In the gcc-3 era the C++ timing performance were really poor, gcc-4
solved a lot such problem.
I guess the situation is improved in the meantime but of course cygwin
is slower than an equivalent
native build as he try to replicate the UNIX/Posix enviroment in an
unfriendly MS-Windows word.

My experience porting octave says that gcc-4 is much better but I have
no idea of ROOT needs.

Regards
Marco

--
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/


  parent reply	other threads:[~2011-01-27 20:07 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)
2011-01-27 20:07   ` marco atzeri [this message]
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=AANLkTimZMLAxHGLvk4ND0RVDo6YiDRd4mDFL7H4twF3F@mail.gmail.com \
    --to=marco.atzeri@gmail.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: link
Be 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).