All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Christopher Cameron <christopher.cameron@live.com>
Cc: git@vger.kernel.org
Subject: Re: Problem with &quot;dashless options&quot;
Date: Tue, 27 Apr 2010 23:28:28 +0200	[thread overview]
Message-ID: <m2eii0egar.fsf@igel.home> (raw)
In-Reply-To: <loom.20100427T194730-644@post.gmane.org> (Christopher Cameron's message of "Tue, 27 Apr 2010 17:55:20 +0000 (UTC)")

Christopher Cameron <christopher.cameron@live.com> writes:

> I encountered the exact same problem.  There are a sequence of
> #defines in parse_options.h which are supposed to initialize option
> structs (OPT_END, OPT_STRING, etc).  These structures only partially 
> initialize the structure, leading to, for instance, junk bits in the flags 
> word of OPT_STRING.

That's a bug in your compiler.  All parts of the struct that are not
explicitly initialized are supposed to be implicitly initialized to
zero.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

      reply	other threads:[~2010-04-27 21:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-09 13:21 Problem with "dashless options" Henrik Tidefelt
2009-09-09 14:34 ` Jeff King
2009-09-09 16:26   ` Henrik Tidefelt
2009-09-09 16:30     ` Pierre Habouzit
2009-09-09 21:12       ` Henrik Tidefelt
2009-09-09 22:49         ` Pierre Habouzit
2010-04-27 17:55 ` Problem with &quot;dashless options&quot; Christopher Cameron
2010-04-27 21:28   ` Andreas Schwab [this message]

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=m2eii0egar.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=christopher.cameron@live.com \
    --cc=git@vger.kernel.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.