From: "Juanma Barranquero" <lekktu@gmail.com>
To: dhruva <dhruvakm@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 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: Thu, 1 Jan 2009 19:03:09 +0100 [thread overview]
Message-ID: <f7ccd24b0901011003h49437a8cxae181503b5a8aab7@mail.gmail.com> (raw)
In-Reply-To: <e3f230850901010457s5ef12f76tcc5d5262ed70ed5d@mail.gmail.com>
On Thu, Jan 1, 2009 at 13:57, dhruva <dhruvakm@gmail.com> wrote:
> I have a shorter patch, not sure it if catches all use cases.
Shorter is not an advantage per se. It is clear that using
ULARGE_INTEGER works; if that's the right thing to do, we can settle
on the cleanest patch afterwards.
My concern is why was it done with long double in the first place.
Perhaps there's some reason of back compatibility with older
compilers.
Juanma
next prev parent reply other threads:[~2009-01-01 18:03 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 [this message]
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
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
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=f7ccd24b0901011003h49437a8cxae181503b5a8aab7@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=dhruvakm@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 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).