public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mjw@redhat.com>
To: elfutils-devel@lists.fedorahosted.org
Subject: Re: [PATCH 1/2] Add is_executable to Dwfl_Module.
Date: Wed, 10 Sep 2014 20:56:48 +0200	[thread overview]
Message-ID: <1410375408.27502.25.camel@bordewijk.wildebeest.org> (raw)
In-Reply-To: 20140910072127.GA1967@host2.jankratochvil.net

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

On Wed, 2014-09-10 at 09:21 +0200, Jan Kratochvil wrote:
> On Tue, 09 Sep 2014 23:55:34 +0200, Roland McGrath wrote:
> > >    int segment;			/* Index of first segment table entry.  */
> > >    bool gc;			/* Mark/sweep flag.  */
> > > +  bool is_executable : 1;	/* Use Dwfl::executable_for_core?  */
> > 
> > If you're going to use a bitfield, then make every other bool in that
> > struct a bitfield too.  But it's not usually worthwhile.  It's
> > premature microoptimization that privileges memory over CPU, which
> > might not even be the right tradeoff any more.
> 
> I really do not mind, up to the maintainer how it all should be.

I don't think it is very helpful or productive to refuse to have a
technical opinion on a fair question about a code change you are
proposing. But if you need a "ruling" to move forward then I am with
Roland that the usage of booleans in a structure should be consistent.
Don't introduce a one-off bool bitfield unless you group the other bools
in the struct together and make them all bitfields. If you are not doing
that, then just make it a regular bool field.

Thanks,

Mark

             reply	other threads:[~2014-09-10 18:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-10 18:56 Mark Wielaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-09-22 17:28 Roland McGrath
2014-09-18 14:59 Jan Kratochvil
2014-09-18 14:56 Mark Wielaard
2014-09-11 19:00 Jan Kratochvil
2014-09-10 20:15 Mark Wielaard
2014-09-10  7:21 Jan Kratochvil
2014-09-09 21:55 Roland McGrath
2014-09-09 21:51 Jan Kratochvil

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=1410375408.27502.25.camel@bordewijk.wildebeest.org \
    --to=mjw@redhat.com \
    --cc=elfutils-devel@lists.fedorahosted.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 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).