public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ian at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/61258] gccgo: assertion failure go-map-delete.c:37 [GoSmith]
Date: Sat, 13 Dec 2014 01:59:00 -0000	[thread overview]
Message-ID: <bug-61258-4-BFK3Tp08nA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61258-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from ian at gcc dot gnu.org <ian at gcc dot gnu.org> ---
Author: ian
Date: Sat Dec 13 01:58:46 2014
New Revision: 218702

URL: https://gcc.gnu.org/viewcvs?rev=218702&root=gcc&view=rev
Log:
    PR go/61258
runtime: Don't crash when deleting zero-sized key.

Modified:
    trunk/libgo/runtime/go-map-delete.c


  parent reply	other threads:[~2014-12-13  1:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-20 18:25 [Bug go/61258] New: gccgo: assertion failure go-map-delete.c:37 dvyukov at google dot com
2014-12-10 21:52 ` [Bug go/61258] gccgo: assertion failure go-map-delete.c:37 [GoSmith] cmang at google dot com
2014-12-13  1:59 ` ian at gcc dot gnu.org [this message]
2015-01-06 14:11 ` cmang at google dot com

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-61258-4-BFK3Tp08nA@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).