public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/113562] [14 Regression] FAIL: gcc.dg/guality/pr54796.c Date: Mon, 29 Jan 2024 14:48:42 +0000 [thread overview] Message-ID: <bug-113562-4-SEgoZjkhqs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113562-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113562 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- Just to put it somewhere I ran dwlocstat on cc1plus before/after the offending change and it looks almost the same. We go from cov% samples cumul 0..10 1280217/38% 1280217/38% 11..20 55668/1% 1335885/40% 21..30 68004/2% 1403889/42% 31..40 70774/2% 1474663/44% 41..50 75554/2% 1550217/46% 51..60 91816/2% 1642033/49% 61..70 101139/3% 1743172/52% 71..80 135281/4% 1878453/56% 81..90 198470/5% 2076923/62% 91..100 1233822/37% 3310745/100% to cov% samples cumul 0..10 1280197/38% 1280197/38% 11..20 55669/1% 1335866/40% 21..30 68014/2% 1403880/42% 31..40 70773/2% 1474653/44% 41..50 75542/2% 1550195/46% 51..60 91800/2% 1641995/49% 61..70 101133/3% 1743128/52% 71..80 135259/4% 1878387/56% 81..90 198496/5% 2076883/62% 91..100 1233844/37% 3310727/100%
next prev parent reply other threads:[~2024-01-29 14:48 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-23 15:55 [Bug debug/113562] New: " hjl.tools at gmail dot com 2024-01-24 8:13 ` [Bug debug/113562] " rguenth at gcc dot gnu.org 2024-01-24 11:00 ` rguenth at gcc dot gnu.org 2024-01-29 14:48 ` rguenth at gcc dot gnu.org [this message] 2024-01-30 7:34 ` rguenth at gcc dot gnu.org 2024-03-07 20:45 ` law at gcc dot gnu.org 2024-05-07 7:44 ` [Bug debug/113562] [14/15 " rguenth 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-113562-4-SEgoZjkhqs@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).