public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109812] GraphicsMagick resize is a lot slower in GCC 13.1 vs Clang 16 Date: Sun, 28 May 2023 16:46:17 +0000 [thread overview] Message-ID: <bug-109812-4-xUZDCKhBnf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109812-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109812 Jan Hubicka <hubicka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hubicka at gcc dot gnu.org --- Comment #6 from Jan Hubicka <hubicka at gcc dot gnu.org> --- I installed the phoronix testuiste and uploaded sample data it uses to http://www.ucw.cz/~hubicka/sample-photo-6000x4000-1.zip I doubt they make much difference especially for resizing.
next prev parent reply other threads:[~2023-05-28 16:46 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-11 14:25 [Bug tree-optimization/109812] New: " aros at gmx dot com 2023-05-11 14:26 ` [Bug tree-optimization/109812] " aros at gmx dot com 2023-05-11 15:20 ` [Bug target/109812] " pinskia at gcc dot gnu.org 2023-05-11 15:50 ` aros at gmx dot com 2023-05-12 8:47 ` aros at gmx dot com 2023-05-16 22:43 ` juzhe.zhong at rivai dot ai 2023-05-17 0:08 ` sjames at gcc dot gnu.org 2023-05-28 16:46 ` hubicka at gcc dot gnu.org [this message] 2023-05-28 17:29 ` [Bug target/109812] GraphicsMagick resize is a lot slower in GCC 13.1 vs Clang 16 on Intel Raptor Lake hubicka at gcc dot gnu.org 2023-05-28 17:39 ` hubicka at gcc dot gnu.org 2023-05-28 18:11 ` hubicka at gcc dot gnu.org 2023-05-28 18:50 ` hubicka at gcc dot gnu.org 2023-05-30 0:05 ` zhangjungcc at gmail dot com 2023-05-31 12:42 ` hubicka at ucw dot cz 2023-05-31 16:11 ` hubicka at gcc dot gnu.org 2023-05-31 16:52 ` jamborm at gcc dot gnu.org 2023-06-01 9:38 ` jamborm at gcc dot gnu.org 2023-06-01 11:19 ` jakub at gcc dot gnu.org 2023-06-01 12:28 ` hubicka at gcc dot gnu.org 2023-06-21 9:46 ` ubizjak at gmail dot com 2023-10-12 4:48 ` cvs-commit at gcc dot gnu.org 2023-11-24 23:38 ` hubicka at gcc dot gnu.org 2023-11-25 10:21 ` liuhongt 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-109812-4-xUZDCKhBnf@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).