This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/14563] octave built under Cygwin very slow
- From: "paulthomas2 at wanadoo dot fr" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 3 Apr 2004 18:24:27 -0000
- Subject: [Bug c++/14563] octave built under Cygwin very slow
- References: <20040312233606.14563.paulthomas2@wanadoo.fr>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From paulthomas2 at wanadoo dot fr 2004-04-03 18:24 -------
Subject: Re: octave built under Cygwin very slow
Sorry, yes, you are right, I can test it but not to see it's effect on
that gruesome cyming special.
Paul
epanelelytha at kellertimo dot de wrote:
>------- Additional Comments From epanelelytha at kellertimo dot de 2004-04-03 18:00 -------
>(In reply to comment #28)
>
>
>>Subject: Re: octave built under Cygwin very slow
>>
>>Hi,
>>
>>It's good to know that you are enagaging with this one. I sent a
>>message this morning that some how got deleted in the process of being
>>sent; it's main content was not to forget that the most extreme
>>manifestation of the difference is with g++ 3.3.1 (cygming special) for
>>which
>>
>>new/delete takes 1900ns/loop
>>malloc/erase 400ns/loop
>>
>>This is how we detected this in the first place.
>>
>>For reference, on the same Athlon 1700, 3.2.2 20030222 (RH 3.2.2-5)
>>
>>Gives
>>
>>new/delete 140ns/loop
>>malloc/erase 100ns/loop
>>
>>Unfortunately, I just this morning deleted the g++ 3.3.1 and replaced it
>>with 3.2 (which does not show such aberrant behaviour, by the way) , so
>>I cannot test your patch!
>>
>>
>But you can still test it with 3.2 (I'm using 3.5-tree-ssa 20040403).
>
>
>
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14563