From: Jeff Law <jeffreyalaw@gmail.com>
To: "Kewen.Lin" <linkw@linux.ibm.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Bill Schmidt <wschmidt@linux.ibm.com>,
bergner@linux.ibm.com,
Segher Boessenkool <segher@kernel.crashing.org>
Subject: Re: [PATCH] pragma: Update target option node when optimization changes [PR103515]
Date: Wed, 8 Dec 2021 18:43:50 -0700 [thread overview]
Message-ID: <dbcac033-5e51-5f4a-0ef7-69ff7aadb595@gmail.com> (raw)
In-Reply-To: <6e9eaac5-3154-6460-1327-5c6afc14e33a@linux.ibm.com>
On 12/6/2021 7:15 PM, Kewen.Lin via Gcc-patches wrote:
> Hi,
>
> For a function with optimize pragma, it's possible that the target
> options change as optimization options change. Now we create one
> optimization option node when parsing pragma optimize, but don't
> create target option node for possible target option changes. It
> makes later processing not detect the target options have actually
> changed and doesn't update the target options accordingly.
>
> This patch is to check whether target options have changed when
> creating one optimization option node for pragma optimize, and
> make one target option node if needed. The associated test case
> shows the difference. Without this patch, the function foo1 will
> perform unrolling which is unexpected. The reason is that flag
> unroll_only_small_loops isn't correctly set for it. The value
> is updated after parsing function foo2, but doesn't get restored
> later since both decls don't have DECL_FUNCTION_SPECIFIC_TARGET
> set and the hook think we don't need to switch. With this patch,
> there is no unrolling for foo1, which is also consistent with the
> behavior by replacing pragma by attribute whether w/ and w/o this
> patch.
>
> Bootstrapped and regtested on x86_64-redhat-linux, aarch64-linux-gnu
> and powerpc64{,le}-linux-gnu.
>
> Is it ok for trunk?
>
> BR,
> Kewen
> ---
> gcc/ChangeLog:
>
> PR target/103515
> * attribs.c (decl_attributes): Check if target options change and
> create one node if so.
>
> gcc/testsuite/ChangeLog:
>
> PR target/103515
> * gcc.target/powerpc/pr103515.c: New test.
OK
jeff
next prev parent reply other threads:[~2021-12-09 1:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 2:15 Kewen.Lin
2021-12-09 1:43 ` Jeff Law [this message]
2021-12-13 6:24 ` Kewen.Lin
2021-12-09 15:21 ` Martin Liška
2021-12-13 6:40 ` Kewen.Lin
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=dbcac033-5e51-5f4a-0ef7-69ff7aadb595@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=bergner@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=linkw@linux.ibm.com \
--cc=segher@kernel.crashing.org \
--cc=wschmidt@linux.ibm.com \
/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).