From: Siva Chandra <sivachandra@google.com>
To: Alan Modra <amodra@gmail.com>
Cc: Ulrich Weigand <uweigand@de.ibm.com>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] PR c++/17494 - Fix evaluation of method calls under EVAL_SKIP
Date: Wed, 05 Nov 2014 00:33:00 -0000 [thread overview]
Message-ID: <CAGyQ6gzKoZTuKY12Mn0iGWpwy98pRNAn1NbXD9z9wbkrLjt2dw@mail.gmail.com> (raw)
In-Reply-To: <20141105002415.GG20070@bubble.grove.modra.org>
Sorry if I am at fault. My compiler is gcc-4.8.2 and I do not see
these errors. I will dig further as soon as I can (which is not likely
until tomorrow).
On Tue, Nov 4, 2014 at 4:24 PM, Alan Modra <amodra@gmail.com> wrote:
> On Mon, Nov 03, 2014 at 06:08:15PM -0800, Siva Chandra wrote:
>> >> PR c++/17494
>> >> * eval.c (evaluate_subexp_standard): Evaluate the "object" and
>> >> the method args also under EVAL_SKIP when evaluating method
>> >> calls under EVAL_SKIP.
>>
>> Thanks for the review. Pushed: e0f52461c2467b6610391681fa27cd9b3c5def57
>
> After this patch, when using gcc-4.9.1 and gcc-5.0 (20140911) I see
> what looks to me to be nonsense errors (ie. I'd suspect a compiler
> bug). Does anyone else see the same? Nothing special in configure
> options, x86_64-linux.
>
> /src/binutils-gdb/gdb/eval.c: In function ‘evaluate_subexp_standard’:
> /src/binutils-gdb/gdb/eval.c:745:16: error: ‘ret’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
> struct value *ret = NULL;
> ^
> In file included from /src/binutils-gdb/gdb/common/common-defs.h:49:0,
> from /src/binutils-gdb/gdb/defs.h:28,
> from /src/binutils-gdb/gdb/eval.c:20:
> /src/binutils-gdb/gdb/common/common-exceptions.h:148:20: error: ‘buf’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
> SIGJMP_BUF *buf = \
> ^
> /src/binutils-gdb/gdb/common/common-exceptions.h:148:20: note: ‘buf’ was declared here
> SIGJMP_BUF *buf = \
> ^
> /src/binutils-gdb/gdb/eval.c:747:2: note: in expansion of macro ‘TRY_CATCH’
> TRY_CATCH (ex, RETURN_MASK_ERROR)
> ^
> /src/binutils-gdb/gdb/eval.c:1429:19: error: ‘value’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
> struct value *value = NULL;
> ^
> In file included from /src/binutils-gdb/gdb/common/common-defs.h:49:0,
> from /src/binutils-gdb/gdb/defs.h:28,
> from /src/binutils-gdb/gdb/eval.c:20:
> /src/binutils-gdb/gdb/common/common-exceptions.h:148:20: error: ‘buf’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
> SIGJMP_BUF *buf = \
> ^
> /src/binutils-gdb/gdb/common/common-exceptions.h:148:20: note: ‘buf’ was declared here
> SIGJMP_BUF *buf = \
> ^
> /src/binutils-gdb/gdb/eval.c:1430:5: note: in expansion of macro ‘TRY_CATCH’
> TRY_CATCH (except, RETURN_MASK_ERROR)
> ^
> /src/binutils-gdb/gdb/eval.c:1846:18: error: ‘value’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
> struct value *value = NULL;
> ^
> In file included from /src/binutils-gdb/gdb/common/common-defs.h:49:0,
> from /src/binutils-gdb/gdb/defs.h:28,
> from /src/binutils-gdb/gdb/eval.c:20:
> /src/binutils-gdb/gdb/common/common-exceptions.h:148:20: error: ‘buf’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
> SIGJMP_BUF *buf = \
> ^
> /src/binutils-gdb/gdb/common/common-exceptions.h:148:20: note: ‘buf’ was declared here
> SIGJMP_BUF *buf = \
> ^
> /src/binutils-gdb/gdb/eval.c:1847:4: note: in expansion of macro ‘TRY_CATCH’
> TRY_CATCH (except, RETURN_MASK_ERROR)
> ^
> cc1: all warnings being treated as errors
>
>
> --
> Alan Modra
> Australia Development Lab, IBM
next prev parent reply other threads:[~2014-11-05 0:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 19:11 Siva Chandra
2014-10-27 17:22 ` Siva Chandra
2014-11-03 14:35 ` Siva Chandra
2014-11-03 15:08 ` Ulrich Weigand
2014-11-04 2:08 ` Siva Chandra
2014-11-05 0:24 ` Alan Modra
2014-11-05 0:33 ` Siva Chandra [this message]
2014-11-05 11:00 ` James Greenhalgh
2014-11-05 12:54 ` Alan Modra
2014-11-10 14:24 ` [push] Work around GCC bug 63748 (Re: [PATCH] PR c++/17494 - Fix evaluation of method calls under EVAL_SKIP) Ulrich Weigand
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=CAGyQ6gzKoZTuKY12Mn0iGWpwy98pRNAn1NbXD9z9wbkrLjt2dw@mail.gmail.com \
--to=sivachandra@google.com \
--cc=amodra@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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