public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "guojiufu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107692] [13 regression] r13-3950-g071e428c24ee8c breaks many test cases
Date: Fri, 18 Nov 2022 13:35:30 +0000	[thread overview]
Message-ID: <bug-107692-4-HqLbqm9Uth@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107692-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Jiu Fu Guo <guojiufu at gcc dot gnu.org> ---
(In reply to Hongyu Wang from comment #6)
> (In reply to Jiu Fu Guo from comment #4)
> cut...
> 
> Yes, I've already posted the patch at
> https://gcc.gnu.org/pipermail/gcc-patches/2022-November/606478.html

One minor finding: 
Like -munroll-only-small-loops on other targets(e.g. rs6000, r13-3950 intends
to enable unrolling and uses this option to control the unroll factor according
to the loop size.  Compare with the previous logic(e.g. for rs6000), the new 
logic will cause: 
-fno-unroll-loops may be unable to prevent rtl_unroll_loops from running, but
loop_unroll_adjust will return 1 to prevent the loop to be unrolled. 
So, there may be side-effects on "slight compiling time" and
"dump-file may be generated with the message of failing to unroll".

  parent reply	other threads:[~2022-11-18 13:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14 21:20 [Bug target/107692] New: " seurer at gcc dot gnu.org
2022-11-14 21:51 ` [Bug target/107692] " pinskia at gcc dot gnu.org
2022-11-15  5:33 ` pinskia at gcc dot gnu.org
2022-11-15  7:02 ` wwwhhhyyy333 at gmail dot com
2022-11-15 11:49 ` segher at gcc dot gnu.org
2022-11-16 13:19 ` rguenth at gcc dot gnu.org
2022-11-18  6:11 ` guojiufu at gcc dot gnu.org
2022-11-18  6:13 ` guojiufu at gcc dot gnu.org
2022-11-18  7:07 ` wwwhhhyyy333 at gmail dot com
2022-11-18 13:35 ` guojiufu at gcc dot gnu.org [this message]
2022-11-18 14:11 ` segher at gcc dot gnu.org
2022-11-18 14:12 ` segher at gcc dot gnu.org
2022-11-18 19:37 ` wwwhhhyyy333 at gmail dot com
2022-11-18 21:44 ` segher at gcc dot gnu.org
2022-11-24  1:20 ` cvs-commit at gcc dot gnu.org
2022-11-24  1:22 ` wwwhhhyyy333 at gmail dot com
2022-12-19 22:53 ` 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-107692-4-HqLbqm9Uth@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).