From: Jan Hubicka <hubicka@ucw.cz>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Richard Biener <rguenther@suse.de>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] ipa-split: Don't split returns_twice functions [PR106923]
Date: Wed, 8 Feb 2023 18:05:43 +0100 [thread overview]
Message-ID: <Y+PWZwyR4/zCPwXt@kam.mff.cuni.cz> (raw)
In-Reply-To: <Y+IO2AZAm6WPtrQh@tucnak>
> Hi!
>
> As discussed in the PR, returns_twice functions are rare/special beasts
> that need special treatment in the cfg, and inside of their bodies
> we don't know which part actually works the weird returns twice way
> (either in the fork/vfork sense, or in the setjmp) and aren't updating
> ab edges to reflect that.
>
> I think easiest is just to never split these, like we already never
> split noreturn or malloc functions.
I think so too - anyone who puts returns twice function on the hot path
should be punished.
>
> Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
>
> 2023-02-07 Jakub Jelinek <jakub@redhat.com>
>
> PR tree-optimization/106923
> * ipa-split.cc (execute_split_functions): Don't split returns_twice
> functions.
>
> * gcc.dg/pr106923.c: New test.
OK,
Thanks!
Honza
>
> --- gcc/ipa-split.cc.jj 2023-01-02 09:32:22.492283737 +0100
> +++ gcc/ipa-split.cc 2023-02-06 14:15:08.343271251 +0100
> @@ -1715,10 +1715,11 @@ execute_split_functions (void)
> struct cgraph_node *node = cgraph_node::get (current_function_decl);
>
> if (flags_from_decl_or_type (current_function_decl)
> - & (ECF_NORETURN|ECF_MALLOC))
> + & (ECF_NORETURN|ECF_MALLOC|ECF_RETURNS_TWICE))
> {
> if (dump_file)
> - fprintf (dump_file, "Not splitting: noreturn/malloc function.\n");
> + fprintf (dump_file, "Not splitting: noreturn/malloc/returns_twice "
> + "function.\n");
> return 0;
> }
> if (MAIN_NAME_P (DECL_NAME (current_function_decl)))
> --- gcc/testsuite/gcc.dg/pr106923.c.jj 2023-02-06 14:19:33.464449400 +0100
> +++ gcc/testsuite/gcc.dg/pr106923.c 2023-02-06 14:18:25.498429162 +0100
> @@ -0,0 +1,23 @@
> +/* PR tree-optimization/106923 */
> +/* { dg-do compile } */
> +/* { dg-options "-O1 -finline-small-functions -fpartial-inlining --param max-inline-insns-single=1 --param uninlined-function-insns=10000" } */
> +
> +int n;
> +
> +int
> +baz (void);
> +
> +__attribute__ ((returns_twice)) int
> +bar (void)
> +{
> + if (baz ())
> + ++n;
> +
> + return 0;
> +}
> +
> +int
> +foo (void)
> +{
> + return bar ();
> +}
>
> Jakub
>
prev parent reply other threads:[~2023-02-08 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 8:42 Jakub Jelinek
2023-02-07 9:26 ` Richard Biener
2023-02-08 17:05 ` Jan Hubicka [this message]
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=Y+PWZwyR4/zCPwXt@kam.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=rguenther@suse.de \
/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).