public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave.anglin at bell dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106458] [12/13 Regression] glibc's malloc/tst-scratch_buffer.c test is miscompiled with gcc-12
Date: Fri, 29 Jul 2022 14:46:44 +0000 [thread overview]
Message-ID: <bug-106458-4-FsWmuEt0IC@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
--- Comment #6 from dave.anglin at bell dot net ---
On 2022-07-29 8:50 a.m., dave.anglin at bell dot net wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106458
>
> --- Comment #5 from dave.anglin at bell dot net ---
> On 2022-07-28 4:12 a.m., rguenth at gcc dot gnu.org wrote:
>> Can you check trunk / the gcc 12 branch head?
> Test fails in the same way with trunk.
Aside from a couple of .stringz and .ident assembler statements, there is no
difference in the assembly code generated
by "GCC: (GNU) 13.0.0 20220728 (experimental) [master r13-1220-g7c1c7e120cc]"
and "GCC: (Debian 12.1.0-7) 12.1.0".
next prev parent reply other threads:[~2022-07-29 14:46 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 [this message]
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
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-FsWmuEt0IC@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).