public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "admin at levyhsu dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/106315] [13 Regression] 7.8% increased codesize on specfp 507.cactuBSSN_r
Date: Mon, 25 Jul 2022 06:30:06 +0000	[thread overview]
Message-ID: <bug-106315-4-BOrZeYzLnq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106315-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106315

--- Comment #4 from Levy Hsu <admin at levyhsu dot com> ---
So I cross-compared all sizes of those .o files in make.out:

list of all diff > 2% files:

Size1: 19464 Size2: 20760 File: PUGH/SetupPGV.o
Size1: 324675 Size2: 402929 File: LocalReduce/CountFunctions.o
Size1: 372967 Size2: 408964 File: LocalReduce/Norm4Functions.o
Size1: 378371 Size2: 434948 File: LocalReduce/Norm1Functions.o
Size1: 370431 Size2: 442340 File: LocalReduce/Norm2Functions.o
Size1: 373212 Size2: 460212 File: LocalReduce/SumFunctions.o
Size1: 373858 Size2: 452466 File: LocalReduce/AvgFunctions.o
Size1: 379238 Size2: 437511 File: LocalReduce/NormInfFunctions.o
Size1: 374379 Size2: 384654 File: LocalReduce/MaxFunctions.o
Size1: 377728 Size2: 387170 File: LocalReduce/MinFunctions.o
Size1: 379068 Size2: 395071 File: LocalReduce/Norm3Functions.o
Size1: 7136496 Size2: 7640664 File: cactusBSSN_r

Not sure if they were caused by the same head file

  parent reply	other threads:[~2022-07-25  6:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-15 14:55 [Bug tree-optimization/106315] New: " admin at levyhsu dot com
2022-07-18  7:34 ` [Bug tree-optimization/106315] [13 Regression] " rguenth at gcc dot gnu.org
2022-07-18  8:50 ` marxin at gcc dot gnu.org
2022-07-21  3:26 ` admin at levyhsu dot com
2022-07-21 15:28 ` hjl.tools at gmail dot com
2022-07-25  6:30 ` admin at levyhsu dot com [this message]
2022-07-29 14:48 ` hjl.tools at gmail dot com
2023-02-21 14:05 ` rguenth at gcc dot gnu.org
2023-04-26  6:56 ` [Bug tree-optimization/106315] [13/14 " rguenth at gcc dot gnu.org
2023-07-27  9:23 ` rguenth at gcc dot gnu.org
2024-03-09 17:16 ` law at gcc dot gnu.org
2024-05-21  9:11 ` [Bug tree-optimization/106315] [13/14/15 " jakub 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-106315-4-BOrZeYzLnq@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).