public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/63504] [5 Regression] Issues found by --enable-checking=valgrind
Date: Wed, 28 Jan 2015 20:31:00 -0000	[thread overview]
Message-ID: <bug-63504-4-oygdbZE05T@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63504-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63504

--- Comment #15 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Wed Jan 28 20:30:30 2015
New Revision: 220216

URL: https://gcc.gnu.org/viewcvs?rev=220216&root=gcc&view=rev
Log:
    PR other/63504
    * dwarf2out.c (add_AT_wide, mem_loc_descriptor, loc_descriptor):
    Use ggc_alloc<wide_int> instead of ggc_cleared_alloc<wide_int>.
    (attr_checksum, attr_checksum_ordered, hash_loc_operands): Checksum
    only get_full_len HOST_WIDE_INTs from get_val () array rather than
    all bits in *val_wide.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/dwarf2out.c


  parent reply	other threads:[~2015-01-28 20:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-10  6:34 [Bug other/63504] New: " trippels at gcc dot gnu.org
2014-10-10  7:35 ` [Bug other/63504] " rguenth at gcc dot gnu.org
2014-10-10  7:37 ` trippels at gcc dot gnu.org
2014-10-10  8:53 ` trippels at gcc dot gnu.org
2014-10-10  9:03 ` trippels at gcc dot gnu.org
2014-10-11  8:04 ` trippels at gcc dot gnu.org
2014-10-11  8:04 ` trippels at gcc dot gnu.org
2014-10-12 14:16 ` trippels at gcc dot gnu.org
2014-10-12 18:13 ` trippels at gcc dot gnu.org
2014-11-20 12:14 ` rguenth at gcc dot gnu.org
2015-01-26 17:57 ` jakub at gcc dot gnu.org
2015-01-26 18:35 ` jakub at gcc dot gnu.org
2015-01-27 19:24 ` jakub at gcc dot gnu.org
2015-01-27 20:17 ` ccoutant at google dot com
2015-01-28 20:31 ` jakub at gcc dot gnu.org [this message]
2015-02-03  9:40 ` jakub at gcc dot gnu.org
2015-02-03  9:40 ` jakub at gcc dot gnu.org
2015-03-09 20:49 ` trippels at gcc dot gnu.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-63504-4-oygdbZE05T@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).