public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/102906] [12 regression] gcc.target/arm/ivopts-4.c fails since r12-4526
Date: Mon, 08 Nov 2021 18:20:37 +0000	[thread overview]
Message-ID: <bug-102906-4-PS38ybETn6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102906-4@http.gcc.gnu.org/bugzilla/>

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

Aldy Hernandez <aldyh at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rguenth at gcc dot gnu.org

--- Comment #10 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
(In reply to Christophe Lyon from comment #9)
> (In reply to Aldy Hernandez from comment #7)
> > > then size ivopts-4.o:
> > >    text    data     bss     dec     hex filename
> > >      38       0       0      38      26 ivopts-4.o
> > > where the testcase expects text <= 36
> > 
> > Ohhhhh, this is an object size regression?  This test seems very fragile. 
> > Jump threading will alter code size, so any change in the threading rules
> > will likely have an effect on code size.  I suggest you add
> > -fno-thread-jumps to the test and adjust the object-size test accordingly.
> 
> I tried that, it doesn't change the generated code.

The difference from before the commit til now is that there was a threading
path that was valid but is now disallowed.  So adding -fno-thread-jumps won't
have any effect since it won't cause the disallowed threading path to reappear.
 What I'm saying is that the test should be calibrated to the new normal.

Of course, it could be that another pass should pick up the slack here, or that
the restriction is too strict.  Richi, do you have some insight here?

At least for -Os  -mthumb -mfloat-abi=hard -mfpu=neon -mtls-dialect=gnu
-mlibarch=armv7-a+mp+sec+neon-fp16 -march=armv7-a+mp+sec+neon-fp16, the
difference in the threader is that we used to thread 6->4->3 in DOM2, but we no
longer do so because doing so would rotate the loop:

a.c.127t.dom2:Path rotates loop:   Cancelling jump thread: (6, 4) incoming
edge;  (4, 3) normal; 

I still think testing for some magic code size is fragile at best.

  parent reply	other threads:[~2021-11-08 18:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-22 23:09 [Bug middle-end/102906] New: " clyon at gcc dot gnu.org
2021-10-25  6:44 ` [Bug middle-end/102906] " rguenth at gcc dot gnu.org
2021-10-30 17:51 ` aldyh at gcc dot gnu.org
2021-11-01 20:09 ` clyon at gcc dot gnu.org
2021-11-06 18:20 ` aldyh at redhat dot com
2021-11-07 10:36 ` clyon at gcc dot gnu.org
2021-11-08  7:12 ` aldyh at gcc dot gnu.org
2021-11-08  7:52 ` clyon at gcc dot gnu.org
2021-11-08  8:19 ` [Bug testsuite/102906] " aldyh at gcc dot gnu.org
2021-11-08  8:41 ` aldyh at gcc dot gnu.org
2021-11-08 17:53 ` clyon at gcc dot gnu.org
2021-11-08 18:20 ` aldyh at gcc dot gnu.org [this message]
2021-11-09  8:15 ` [Bug tree-optimization/102906] " rguenth at gcc dot gnu.org
2021-11-10  9:15 ` aldyh at gcc dot gnu.org
2021-11-10  9:18 ` rguenther at suse dot de
2021-11-10  9:53 ` aldyh at gcc dot gnu.org
2021-11-10  9:57 ` rguenther at suse dot de
2021-11-10 10:07 ` aldyh at gcc dot gnu.org
2021-11-10 10:13 ` rguenther at suse dot de
2021-11-10 10:20 ` aldyh at redhat dot com
2021-11-10 12:59 ` aldyh at gcc dot gnu.org
2021-11-10 22:13 ` cvs-commit at gcc dot gnu.org
2021-11-11  6:19 ` aldyh at gcc dot gnu.org
2021-11-14 10:39 ` aldyh 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-102906-4-PS38ybETn6@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).