public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/109306] The strstr implementation in libiberty might have undefined behavior (out of bounds mem access) Date: Mon, 27 Mar 2023 19:27:43 +0000 [thread overview] Message-ID: <bug-109306-4-bGPWjy6XCK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109306-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109306 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|The strstr function might |The strstr implementation |do undefined behavior (out |in libiberty might have |of bounds mem access) |undefined behavior (out of | |bounds mem access) Component|c |other --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- I highly doubt strstr.c inside libiberty is used on any host in the last 10 years or so since strstr is C90/c++98 and GCC requires a C++11 compiler/library as a host.
next prev parent reply other threads:[~2023-03-27 19:27 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-27 19:24 [Bug c/109306] New: The strstr function might do " pmorf at apple dot com 2023-03-27 19:27 ` pinskia at gcc dot gnu.org [this message] 2023-03-27 19:34 ` [Bug other/109306] The strstr implementation in libiberty might have " pmorf at apple dot com 2023-03-27 19:37 ` pinskia at gcc dot gnu.org 2023-03-27 19:40 ` pmorf at apple dot com 2023-03-27 19:46 ` jakub at gcc dot gnu.org 2023-03-27 19:48 ` jakub at gcc dot gnu.org 2023-04-02 18:07 ` cvs-commit at gcc dot gnu.org 2023-04-02 18:14 ` jakub at gcc dot gnu.org 2023-04-18 7:16 ` cvs-commit at gcc dot gnu.org 2023-05-02 20:16 ` cvs-commit at gcc dot gnu.org 2023-05-03 15:23 ` cvs-commit 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-109306-4-bGPWjy6XCK@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: linkBe 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).