unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: dhruva <dhruvakm@gmail.com>
To: "Jason Rumney" <jasonr@gnu.org>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Profiling Emacs on M$
Date: Wed, 21 May 2008 14:44:16 +0530	[thread overview]
Message-ID: <e3f230850805210214i59ba1042ocb7269241aacb996@mail.gmail.com> (raw)
In-Reply-To: <4833D500.30207@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]

Hello,

On 5/21/08, Jason Rumney <jasonr@gnu.org> wrote:
> redisplay functions dominate.  When I do this using Free profiling software
> (gprof), it shows w32font_text_extents as being the most significant
> consumer of CPU time outside of garbage collection and waiting for input. It
> would be interesting if you can replicate those results, as that would prove
> that using proprietary software does not give any advantage here.
>

Both tools give the same information, hence the point is proved.
Anyway, I was not trying to argue on that aspect, just that I am used
to kernrate (when you build using MSVC).
I normally used to build using MinGW/GCC but felt the need to work on
getting back the MSVC build too. I still find debugging with GDB on M$
not as good as debugging on GNU/Linux. Easier to use proprietary
debuggers on M$ as they can handle crash files which GDB cannot in its
current state. So, the lack of proper debugging support in GDB for M$
makes my use MSVC.

-dky

-- 
Contents reflect my personal views only!

[-- Attachment #2: emacs_kernrate.png --]
[-- Type: image/png, Size: 22878 bytes --]

  reply	other threads:[~2008-05-21  9:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-21  4:54 Profiling Emacs on M$ dhruva
2008-05-21  7:53 ` Jason Rumney
2008-05-21  9:14   ` dhruva [this message]
2008-05-21 17:18     ` Eli Zaretskii
2008-05-22  3:55       ` dhruva
2008-05-23  8:22         ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e3f230850805210214i59ba1042ocb7269241aacb996@mail.gmail.com \
    --to=dhruvakm@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=jasonr@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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).