public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/106458] [12/13 Regression] glibc's malloc/tst-scratch_buffer.c test is miscompiled with gcc-12 Date: Sat, 05 Nov 2022 20:54:07 +0000 [thread overview] Message-ID: <bug-106458-4-vzCr9m1YIz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106458-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106458 John David Anglin <danglin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #17 from John David Anglin <danglin at gcc dot gnu.org> --- glibc issue: commit 8c77e26ba8b360c851b2b9485bb4431aacc51ad1 Author: Szabolcs Nagy <szabolcs.nagy@arm.com> Date: Tue Oct 11 13:23:25 2022 +0100 Remove unused scratch_buffer_dupfree Turns out scratch_buffer_dupfree internal API was unused since commit ef0700004bf0dccf493a5e8e21f71d9e7972ea9f stdlib: Simplify buffer management in canonicalize And the related test in malloc/tst-scratch_buffer had issues so it's better to remove it completely.
next prev parent reply other threads:[~2022-11-05 20:54 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-27 19:40 [Bug target/106458] New: [12 " danglin at gcc dot gnu.org 2022-07-27 19:41 ` [Bug target/106458] " danglin at gcc dot gnu.org 2022-07-27 19:42 ` danglin at gcc dot gnu.org 2022-07-27 19:42 ` danglin at gcc dot gnu.org 2022-07-28 8:12 ` [Bug target/106458] [12/13 " rguenth at gcc dot gnu.org 2022-07-29 12:50 ` dave.anglin at bell dot net 2022-07-29 14:46 ` dave.anglin at bell dot net 2022-07-30 7:09 ` sam at gentoo dot org 2022-08-04 14:14 ` [Bug tree-optimization/106458] " danglin at gcc dot gnu.org 2022-08-07 22:22 ` danglin at gcc dot gnu.org 2022-08-07 22:23 ` danglin at gcc dot gnu.org 2022-08-10 13:30 ` rguenth at gcc dot gnu.org 2022-08-10 14:53 ` dave.anglin at bell dot net 2022-08-10 17:38 ` dave.anglin at bell dot net 2022-08-10 18:12 ` dave.anglin at bell dot net 2022-08-10 20:53 ` dave.anglin at bell dot net 2022-11-05 20:54 ` danglin at gcc dot gnu.org [this message] 2022-11-06 6:39 ` pinskia 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-106458-4-vzCr9m1YIz@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).