Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: asmwarrior <asmwarrior@gmail.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [msys+mingw] build error [-Werror=uninitialized]
Date: Fri, 16 Mar 2012 07:31:00 -0000	[thread overview]
Message-ID: <4F62EC5C.1050609@gmail.com> (raw)
In-Reply-To: <4F62EAC8.8020000@codesourcery.com>

On 2012-3-16 15:24, Yao Qi wrote:
> I didn't see any other errors.  What error did you see even after you
> setting `addr' to 0?
See:

TRY_CATCH (ex, RETURN_MASK_ERROR)
     {
       addr = value_as_address (vfn);
     }
Which means addr is set before passed to print_function_pointer_address() call.
So I'm not sure why gcc report such warning.

Yuanhui Zhang




  reply	other threads:[~2012-03-16  7:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-16  1:56 asmwarrior
2012-03-16  7:26 ` Yao Qi
2012-03-16  7:31   ` asmwarrior [this message]
2012-03-16  7:45     ` Yao Qi
2012-03-16  8:19       ` [commit] " Jan Kratochvil
2012-03-16  8:23         ` asmwarrior
2012-03-16 14:09           ` asmwarrior

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=4F62EC5C.1050609@gmail.com \
    --to=asmwarrior@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=yao@codesourcery.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