public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/66354] [UBSAN] stl_algobase.h:708:7: runtime error: null pointer passed as argument
Date: Mon, 08 Jun 2015 14:19:00 -0000	[thread overview]
Message-ID: <bug-66354-4-em006xbU6q@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66354-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Mon Jun  8 14:19:10 2015
New Revision: 224230

URL: https://gcc.gnu.org/viewcvs?rev=224230&root=gcc&view=rev
Log:
        PR libstdc++/66354
        * include/bits/stl_algobase.h (__fill_a): Check length before calling
        memset.

        PR libstdc++/66327
        * include/bits/stl_algobase.h (__equal<true>::equal): Do not call
        memcmp for empty ranges.
        (__lexicographical_compare<true>::__lc): Likewise.

Modified:
    branches/gcc-5-branch/libstdc++-v3/ChangeLog
    branches/gcc-5-branch/libstdc++-v3/include/bits/stl_algobase.h


  parent reply	other threads:[~2015-06-08 14:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-31 20:40 [Bug libstdc++/66354] New: " dimhen at gmail dot com
2015-05-31 21:32 ` [Bug libstdc++/66354] " redi at gcc dot gnu.org
2015-05-31 21:35 ` redi at gcc dot gnu.org
2015-05-31 22:42 ` redi at gcc dot gnu.org
2015-06-01 19:41 ` dimhen at gmail dot com
2015-06-08 14:19 ` redi at gcc dot gnu.org [this message]
2015-06-08 14:42 ` redi at gcc dot gnu.org
2015-06-08 14:44 ` redi 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-66354-4-em006xbU6q@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).