From: Robert Millan <rmh@aybabtu.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Imminent bugfix release (1.97.1)
Date: Mon, 9 Nov 2009 19:25:18 +0100 [thread overview]
Message-ID: <20091109182518.GA14767@thorin> (raw)
In-Reply-To: <4AF85C54.3080302@gmail.com>
On Mon, Nov 09, 2009 at 07:15:48PM +0100, Vladimir 'phcoder' Serbinenko wrote:
> Robert Millan wrote:
> >
> > Actually, modern CPUs are very complex and the number of operations (or
> > time taken by them) isn't easy to predict.
> >
> >
> It's generally a good practice to do exactly same operations
> independently of result just store the result in a separate variable
> it's how RSA is correctly implemented
>
> for (n = grub_strlen (s1); n >= 0; n--)
> {
> if (*s1 != *s2)
> ret |= 1;
> else
> ret |= 0;
Uhm I didn't check, but I'd suspect -Os would optimize this out.
Anyhow, if we move the fixed time wait to the outer loop, it should no
longer be a problem.
We could also check the approach taken by e.g. su from coreutils.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2009-11-09 18:25 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 1:04 Imminent bugfix release (1.97.1) Robert Millan
2009-11-09 1:27 ` Robert Millan
2009-11-09 2:08 ` Jordan Uggla
2009-11-09 14:15 ` Robert Millan
2009-11-09 13:33 ` Bean
2009-11-09 13:50 ` Vladimir 'phcoder' Serbinenko
2009-11-09 14:18 ` Robert Millan
2009-11-09 14:21 ` Bean
2009-11-09 14:34 ` Vladimir 'phcoder' Serbinenko
2009-11-09 17:46 ` Duboucher Thomas
2009-11-09 18:10 ` Robert Millan
2009-11-09 18:15 ` Vladimir 'phcoder' Serbinenko
2009-11-09 18:25 ` Robert Millan [this message]
2009-11-09 18:36 ` Bean
2009-11-09 18:46 ` Vladimir 'phcoder' Serbinenko
2009-11-09 18:49 ` Bean
2009-11-09 21:13 ` Duboucher Thomas
2009-11-09 21:34 ` Vladimir 'phcoder' Serbinenko
2009-11-09 21:43 ` Duboucher Thomas
2009-11-09 22:06 ` Robert Millan
2009-11-09 22:46 ` Duboucher Thomas
2009-11-09 23:09 ` Darron Black
2009-11-09 23:50 ` richardvoigt
2009-11-09 23:56 ` Darron Black
2009-11-09 23:46 ` richardvoigt
2009-11-10 5:39 ` Bean
2009-11-10 8:28 ` Bean
2009-11-10 8:46 ` Bean
2009-11-10 8:52 ` Bean
2009-11-10 9:05 ` Bean
2009-11-10 12:37 ` Bean
2009-11-10 14:25 ` Duboucher Thomas
2009-11-10 14:47 ` Bean
2009-11-10 17:43 ` Duboucher Thomas
2009-11-10 19:01 ` Vladimir 'phcoder' Serbinenko
2009-11-10 19:04 ` Vladimir 'phcoder' Serbinenko
2009-11-10 21:29 ` Duboucher Thomas
2009-11-10 15:27 ` richardvoigt
2009-11-10 17:38 ` Duboucher Thomas
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=20091109182518.GA14767@thorin \
--to=rmh@aybabtu.com \
--cc=grub-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.
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.