all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Juanma Barranquero" <lekktu@gmail.com>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Optimized gcc 4.3.0 build on Windows returns 0 secs for all time values of system-process-attributes
Date: Sat, 3 Jan 2009 18:14:05 +0100	[thread overview]
Message-ID: <f7ccd24b0901030914u7e4f72c2h268e50491ea458ca@mail.gmail.com> (raw)
In-Reply-To: <usko0mipf.fsf@gnu.org>

On Sat, Jan 3, 2009 at 17:56, Eli Zaretskii <eliz@gnu.org> wrote:

> It's probably worth reporting that to the GCC mailing list, and/or
> file a bug report with them.

Yes, will do.

> Please install your change, but please try making the code more
> concise and clear, if possible.  For example, you could introduce a
> macro or an inline function for this repeated pattern:
>
>> +  tem1.LowPart = ft_kernel.dwLowDateTime;
>> +  tem1.HighPart = ft_kernel.dwHighDateTime;
>> +  tem1.QuadPart /= 10L;

The patch I was using locally already has two macros:

  #define CONVERT_TO_ULARGE(result, ft, div)   \
    do {                                       \
      (result).LowPart = (ft).dwLowDateTime;   \
      (result).HighPart = (ft).dwHighDateTime; \
      if (div)                                 \
        (result).QuadPart /= (div);            \
    } while (0)

  #define TO_LISP_OBJECT(time) ltime ((time).QuadPart / 1000000L,
(time).QuadPart % 1000000L)

so most conversions are like this:

 CONVERT_TO_ULARGE (tem1, ft_kernel, 10L);
 *stime = TO_LISP_OBJECT (tem1);

(better names are very welcome).

> In addition, please also change the other user of convert_time_raw
> similarly to this.

Yes, of course.

    Juanma




  reply	other threads:[~2009-01-03 17:14 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-31 13:00 Optimized gcc 4.3.0 build on Windows returns 0 secs for all time values of system-process-attributes Juanma Barranquero
2008-12-31 17:29 ` dhruva
2008-12-31 19:12 ` Eli Zaretskii
2009-01-01  4:38   ` Juanma Barranquero
2009-01-01 12:57     ` dhruva
2009-01-01 13:08       ` dhruva
2009-01-01 13:16       ` Jason Rumney
2009-01-01 13:43         ` dhruva
2009-01-01 19:00           ` Eli Zaretskii
2009-01-02  4:59             ` dhruva
2009-01-02 14:33               ` Eli Zaretskii
2009-01-02 17:44                 ` Chetan Pandya
2009-01-01 18:03       ` Juanma Barranquero
2009-01-01 18:54     ` Eli Zaretskii
2009-01-03  2:27       ` Juanma Barranquero
2009-01-03 12:29         ` Eli Zaretskii
2009-01-03 13:28           ` Juanma Barranquero
2009-01-03 13:53             ` Juanma Barranquero
2009-01-03 15:33               ` Eli Zaretskii
2009-01-03 16:00                 ` Juanma Barranquero
2009-01-03 16:40                   ` Eli Zaretskii
2009-01-03 16:56                   ` Eli Zaretskii
2009-01-03 17:14                     ` Juanma Barranquero [this message]
2009-01-03 19:02                       ` Eli Zaretskii
2009-01-04  2:24                       ` Jason Rumney
2009-01-04  2:30                         ` Juanma Barranquero
2009-01-04  2:33                           ` Jason Rumney
2009-01-04  2:35                             ` Juanma Barranquero

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=f7ccd24b0901030914u7e4f72c2h268e50491ea458ca@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.