trinity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Vinson Lee <vlee@twopensource.com>
Cc: trinity@vger.kernel.org
Subject: Re: GCC 4.9 build error child.c:274:14: error: variable 'lastop' might be clobbered by 'longjmp' or 'vfork' [-Werror=clobbered]
Date: Tue, 15 Apr 2014 23:27:46 -0400	[thread overview]
Message-ID: <20140416032746.GA10266@redhat.com> (raw)
In-Reply-To: <CAHTgTXUQO_5zCZuW_bYE0Vk473=K0-_qR7ZzfghEOKr381Ov=g@mail.gmail.com>

On Mon, Apr 14, 2014 at 11:42:11AM -0700, Vinson Lee wrote:
 > This build error occurs with GCC 4.9.
 > 
 > $ gcc --version
 > gcc (GCC) 4.9.0 20140411 (Red Hat 4.9.0-0.10)
 > Copyright (C) 2014 Free Software Foundation, Inc.
 > This is free software; see the source for copying conditions.  There is NO
 > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
 > 
 > $ make
 > [...]
 >   CC    child.o
 > child.c: In function 'child_process':
 > child.c:274:14: error: variable 'lastop' might be clobbered by
 > 'longjmp' or 'vfork' [-Werror=clobbered]
 >   const char *lastop = NULL;
 >               ^

heh, I had a hard disk accident last weekend, so hadn't gotten around to
trying 4.9 until this morning.  Should be fixed now.
Was actually quite surprised this was the only new warning.

	Dave

      reply	other threads:[~2014-04-16  3:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-14 18:42 GCC 4.9 build error child.c:274:14: error: variable 'lastop' might be clobbered by 'longjmp' or 'vfork' [-Werror=clobbered] Vinson Lee
2014-04-16  3:27 ` Dave Jones [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=20140416032746.GA10266@redhat.com \
    --to=davej@redhat.com \
    --cc=trinity@vger.kernel.org \
    --cc=vlee@twopensource.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;
as well as URLs for NNTP newsgroup(s).