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: Fri, 28 Jan 2011 05:14:00 -0000	[thread overview]
Message-ID: <AANLkTi=u+BpH-KEUV1a6qgnDjJKndT7j=i96bT1XM-JY@mail.gmail.com> (raw)
In-Reply-To: <4D41F014.5070408@alice.it>

On Thu, Jan 27, 2011 at 11:22 PM, Angelo Graziosi  wrote:
> Marco Atzeri wrote:
>>
>> 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.
>
> I follow the development of ROOT under Cygwin since ROOT-3, and there wasn't
> really big problems: each time, when prompted, they was always fixed by ROOT
> people.
>
> The performances of ROOT under Cygwin are good enough (at least with by
> builds with gcc4 compilers). Obviously Cygwin isn't a native GNU/Linux and
> often the performances are influenced by AV security applications..
>
> Ciao,
> Angelo.

the last is true but AntiVirus affect negatively also native
MS-Windows application :-((
so it is not a cygwin problem.

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/


  reply	other threads:[~2011-01-28  5:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-27 22:22 Angelo Graziosi
2011-01-28  5:14 ` marco atzeri [this message]
     [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

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='AANLkTi=u+BpH-KEUV1a6qgnDjJKndT7j=i96bT1XM-JY@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).