public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "michael.meier at hexagon dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/107415] RISCV-gcc: Leaf function compiles as recursive with -O3
Date: Wed, 26 Oct 2022 12:13:57 +0000 [thread overview]
Message-ID: <bug-107415-4-WGPXC7xnqu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107415-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107415
--- Comment #2 from Michael Meier <michael.meier at hexagon dot com> ---
(In reply to Andrew Pinski from comment #1)
> Gcc can detect memset and optimize it to memset. And this is what is
> happening.
> This is documented too.
Thanks for your quick reply. I understand what is happening now.
Now that you pointed me in this direction, I found many references to this
behavior only, including that I can use -fno-tree-loop-distribute-patterns to
disable the optimization. However I didn't find mention of the feature in the
official documentation. Can you provide me with a reference, please?
next prev parent reply other threads:[~2022-10-26 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 11:57 [Bug c/107415] New: " michael.meier at hexagon dot com
2022-10-26 12:05 ` [Bug tree-optimization/107415] " pinskia at gcc dot gnu.org
2022-10-26 12:13 ` michael.meier at hexagon dot com [this message]
2022-10-26 17:06 ` 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-107415-4-WGPXC7xnqu@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).