public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/85640] [8/9/10/11 Regression] code size regression vs 7.x Date: Wed, 03 Feb 2021 18:09:22 +0000 [thread overview] Message-ID: <bug-85640-4-oRPhhXiIbP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-85640-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85640 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Bisection on size shows r8-1162-gba00284cedbcb0b980af4e5e41f427581af64462 as the first size difference, then r9-2350-gf80d6a178ed2043c6a9a4d8076cdc72d61b67b2b for a smaller growth, r11-3874-gec5e6467091ee0f8de2f894f0c1669465a8440f1 was apparently a temporary growth only, r11-4569-g33c0f246f799b7403171e97f31276a8feddd05c9 grew the other Adler32 function. Anyway, the first one seems to be the largest size difference.
next parent reply other threads:[~2021-02-03 18:09 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-85640-4@http.gcc.gnu.org/bugzilla/> 2021-02-03 18:09 ` jakub at gcc dot gnu.org [this message] 2021-02-03 18:36 ` jakub at gcc dot gnu.org 2021-05-14 9:50 ` [Bug target/85640] [9/10/11/12 " jakub at gcc dot gnu.org 2021-06-01 8:11 ` rguenth at gcc dot gnu.org 2022-05-27 9:39 ` [Bug target/85640] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:35 ` jakub at gcc dot gnu.org 2023-07-07 10:33 ` [Bug target/85640] [11/12/13/14 " rguenth at gcc dot gnu.org 2024-02-22 21:52 ` 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-85640-4-oRPhhXiIbP@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).