Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: jan.kratochvil@redhat.com, gdb-patches@sourceware.org
Subject: Re: [patch 3/4] Fix hw watchpoints #2: reordered / simultaneously	hit
Date: Tue, 17 Nov 2009 22:18:00 -0000	[thread overview]
Message-ID: <83d43gn6dd.fsf@gnu.org> (raw)
In-Reply-To: <20091117194110.GC5266@adacore.com>

> Date: Tue, 17 Nov 2009 14:41:10 -0500
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb-patches@sourceware.org
> 
> > This is what I remembered, at least for x86.  A single additional
> > instruction can hardly cause any visible slowdown, at least not with
> > access patterns typical for such flags.
> > 
> > Any other reasons not to use bitfields?
> 
> No. I just think it is unnecessary, and I'd rather avoid them.  If you are
> so strongly opinionated about this, or if others agree with you that it
> is better, I really don't mind all that much.

I don't have strong opinions either way.  I was just surprised that
you seemed to have opinions strong enough to comment on the usage of
bitfields in Jan's code.

FWIW, I've seen lots of good code using bitfields.  Emacs comes to
mind.  I've also seen lots of code that didn't use them.  I don't
think we should care too much about this, except, as you point out,
when memory is or could be at a premium.


  reply	other threads:[~2009-11-17 22:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-16  3:42 Jan Kratochvil
2009-11-17  0:12 ` Joel Brobecker
2009-11-17  4:03   ` Eli Zaretskii
2009-11-17 14:13     ` Joel Brobecker
2009-11-17 15:31       ` Jan Kratochvil
2009-11-17 19:18         ` Eli Zaretskii
2009-11-17 19:42           ` Joel Brobecker
2009-11-17 22:18             ` Eli Zaretskii [this message]
2009-11-17 19:20       ` Eli Zaretskii
2009-11-18 10:09   ` Jan Kratochvil
2009-11-18 11:36     ` Pedro Alves
2009-11-20 16:58     ` Pedro Alves
2009-11-20 17:06       ` Pedro Alves
2009-11-20 17:15         ` Jan Kratochvil
2009-11-20 17:10       ` Daniel Jacobowitz

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=83d43gn6dd.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox