From: Richard Biener <richard.guenther@gmail.com>
To: Martin Sebor <msebor@gmail.com>
Cc: Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] squash spurious warnings in dominance.c
Date: Mon, 24 Apr 2017 07:41:00 -0000 [thread overview]
Message-ID: <CAFiYyc0cfumUgP4ieG6tuuZrLwm1sOc+xzndE9HEpbJhqD6Q=Q@mail.gmail.com> (raw)
In-Reply-To: <b79b6819-8e7d-3a88-c560-107865c35bb5@gmail.com>
On Sat, Apr 22, 2017 at 2:51 AM, Martin Sebor <msebor@gmail.com> wrote:
> Bug 80486 - spurious -Walloc-size-larger-than and
> -Wstringop-overflow in dominance.c during profiledbootstrap
> points out a number of warnings that show up in dominance.c
> during a profiledbootstrap. I'm pretty sure the warnings
> are due to the size check the C++ new expression introduces
> to avoid unsigned overflow before calling operator new, and
> by some optimization like jump threading introducing a branch
> with the call to the allocation function and memset with
> the excessive constant size.
>
> Two ways to avoid it come to mind: 1) use the libiberty
> XCNEWVEC and XNEWVEC macros instead of C++ new expressions,
> and 2) constraining the size variable to a valid range.
>
> Either of these approaches should result in better code than
> the new expression because they both eliminate the test for
> the overflow. Attached is a patch that implements (1). I
> chose it mainly because it seems in line with GCC's memory
> management policy and with avoiding exceptions.
>
> An alternate patch should be straightforward. Either add
> an assert like the one below or change the type of
> m_n_basic_blocks from size_t to unsigned. This approach,
> though less intrusive, will likely bring the warning back
> in ILP32 builds; I'm not sure if it matters.
Please change m_n_basic_blocks (and local copies) from size_t
to unsigned int. This is an odd inconsistency that's worth fixing
in any case.
Richard.
> Martin
>
> diff --git a/gcc/dominance.c b/gcc/dominance.c
> index c76e62e..ebb0a8f 100644
> --- a/gcc/dominance.c
> +++ b/gcc/dominance.c
> @@ -161,6 +161,9 @@ void
> dom_info::dom_init (void)
> {
> size_t num = m_n_basic_blocks;
> +
> + gcc_assert (num < SIZE_MAX / sizeof (basic_block) / 2);
> +
> m_dfs_parent = new_zero_array <TBB> (num);
> m_dom = new_zero_array <TBB> (num);
>
next prev parent reply other threads:[~2017-04-24 7:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-22 13:49 Martin Sebor
2017-04-24 7:41 ` Richard Biener [this message]
2017-04-24 21:20 ` Martin Sebor
2017-04-25 10:03 ` Richard Biener
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='CAFiYyc0cfumUgP4ieG6tuuZrLwm1sOc+xzndE9HEpbJhqD6Q=Q@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=msebor@gmail.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).