public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/17132] Improper evaluation of expressions involving virtual method invocations under EVAL_AVOID_SIDE_EFFECTS
Date: Sat, 16 Aug 2014 01:33:00 -0000	[thread overview]
Message-ID: <bug-17132-4717-U1Ss39g3Fg@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17132-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=17132

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gdb and binutils".

The branch, master has been updated
       via  e66d44466912ecf581f6b67ff299d064c7bf4f1a (commit)
      from  940df408121be31beed22ef7a5ad133cb1592726 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=e66d44466912ecf581f6b67ff299d064c7bf4f1a

commit e66d44466912ecf581f6b67ff299d064c7bf4f1a
Author: Siva Chandra <sivachandra@chromium.org>
Date:   Wed Jul 9 10:25:48 2014 -0700

    Add new argument NOSIDE to find_overload_match.

    This is a fix for PR c++/17132.
    If this new argument is set to EVAL_AVOID_SIDE_EFFECTS, then the object's
    memory will not be read while picking the best overload match.

    gdb/

        * eval.c: Update all calls to find_overload_match.
        * valarith.c: Likewise.
        (value_user_defined_cpp_op, value_user_defined_op): New
        argument NOSIDE.  Update all callers.
        * valops.c (find_overload_match): New argument NOSIDE.
        * value.h (find_overload_match): Update signature.

    gdb/testsuite

        * gdb.cp/pr17132.cc: New file.
        * gdb.cp/pr17132.exp: New file.

-----------------------------------------------------------------------

Summary of changes:
 gdb/ChangeLog                    |   10 ++++++
 gdb/eval.c                       |    6 ++--
 gdb/testsuite/ChangeLog          |    6 ++++
 gdb/testsuite/gdb.cp/pr17132.cc  |   61 ++++++++++++++++++++++++++++++++++++++
 gdb/testsuite/gdb.cp/pr17132.exp |   40 +++++++++++++++++++++++++
 gdb/valarith.c                   |   15 +++++----
 gdb/valops.c                     |   19 +++++++++--
 gdb/value.h                      |    3 +-
 8 files changed, 146 insertions(+), 14 deletions(-)
 create mode 100644 gdb/testsuite/gdb.cp/pr17132.cc
 create mode 100644 gdb/testsuite/gdb.cp/pr17132.exp

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2014-08-16  1:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09  0:33 [Bug c++/17132] New: " sivachandra at gmail dot com
2014-07-09  0:35 ` [Bug c++/17132] " sivachandra at gmail dot com
2014-08-16  1:33 ` cvs-commit at gcc dot gnu.org [this message]
2023-12-26 18:24 ` ssbssa at sourceware dot org

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=bug-17132-4717-U1Ss39g3Fg@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).