From: Patrick Palka <patrick@parcs.ath.cx>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Pedro Alves <palves@redhat.com>,
gdb-patches@sourceware.org,
Phil Muldoon <pmuldoon@redhat.com>
Subject: Re: [commit] [PATCH v5 6/7] compile: New 'compile print'
Date: Sat, 16 May 2015 14:25:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.11.1505161022240.2479@idea> (raw)
In-Reply-To: <20150516125814.GE9862@host1.jankratochvil.net>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1402 bytes --]
GCC 4.9 emits -Wmaybe-uninitialized warnings for the function get_out_value_type():
/home/patrick/code/binutils-gdb/gdb/compile/compile-object-load.c: In function Β‘compile_object_loadΒ’:
/home/patrick/code/binutils-gdb/gdb/compile/compile-object-load.c:419:20: error: Β‘blockΒ’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
gdb_ptr_type_sym = block_lookup_symbol (block, COMPILE_I_EXPR_PTR_TYPE,
^
/home/patrick/code/binutils-gdb/gdb/compile/compile-object-load.c:376:23: note: Β‘blockΒ’ was declared here
const struct block *block;
^
/home/patrick/code/binutils-gdb/gdb/compile/compile-object-load.c:416:12: error: Β‘gdb_val_symΒ’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
gdb_type = SYMBOL_TYPE (gdb_val_sym);
^
/home/patrick/code/binutils-gdb/gdb/compile/compile-object-load.c:374:37: note: Β‘gdb_val_symΒ’ was declared here
struct symbol *gdb_ptr_type_sym, *gdb_val_sym;
^
/home/patrick/code/binutils-gdb/gdb/compile/compile-object-load.c:406:10: error: Β‘functionΒ’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
if (function != NULL
^
/home/patrick/code/binutils-gdb/gdb/compile/compile-object-load.c:387:22: note: Β‘functionΒ’ was declared here
struct symbol *function;
next prev parent reply other threads:[~2015-05-16 14:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 20:16 [PATCH v5 0/7] compile: compile print (&unmap) Jan Kratochvil
2015-05-13 20:16 ` [PATCH v5 4/7] compile: Use -Wall, not -w Jan Kratochvil
2015-05-15 16:49 ` Pedro Alves
2015-05-16 12:43 ` [commit] " Jan Kratochvil
2015-05-13 20:16 ` [PATCH v5 3/7] compile: Distribute scope, add scope_data Jan Kratochvil
2015-05-15 16:49 ` Pedro Alves
2015-05-16 12:39 ` [commit] " Jan Kratochvil
2015-05-13 20:16 ` [PATCH v5 1/7] compile: Add one debug message Jan Kratochvil
2015-05-15 16:49 ` Pedro Alves
2015-05-16 12:19 ` [commit] " Jan Kratochvil
2015-05-16 13:09 ` [patch] compile: gdb_stdout -> gdb_stdlog [compile: Add one debug message] Jan Kratochvil
2015-05-19 11:47 ` Pedro Alves
2015-05-19 12:28 ` [commit] " Jan Kratochvil
2015-05-13 20:16 ` [PATCH v5 2/7] Code cleanup: Make parts of print_command_1 public Jan Kratochvil
2015-05-16 12:27 ` [commit] " Jan Kratochvil
2015-05-13 20:17 ` [PATCH v5 7/7] RFC only: compile: Use also inferior munmap Jan Kratochvil
2015-05-13 20:17 ` [PATCH v5 6/7] compile: New 'compile print' Jan Kratochvil
2015-05-15 17:04 ` Pedro Alves
2015-05-16 12:58 ` [commit] " Jan Kratochvil
2015-05-16 13:39 ` [commit#2] " Jan Kratochvil
2015-05-16 14:25 ` Patrick Palka [this message]
2015-05-16 14:39 ` [obv] [commit] " Jan Kratochvil
2015-05-13 20:17 ` [PATCH v5 5/7] Code cleanup: compile: func_addr -> func_sym Jan Kratochvil
2015-05-15 16:51 ` Pedro Alves
2015-05-16 12:45 ` [commit] " 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=alpine.DEB.2.11.1505161022240.2479@idea \
--to=patrick@parcs.ath.cx \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=palves@redhat.com \
--cc=pmuldoon@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