From: Jonathan Yong <10walls@gmail.com>
To: Gcc Patch List <gcc-patches@gcc.gnu.org>
Cc: NightStrike <nightstrike@gmail.com>
Subject: Re: [Patch] c-c++-common/Warray-bounds.c: fix excess warnings on LLP64
Date: Wed, 29 Mar 2023 04:48:08 +0000 [thread overview]
Message-ID: <a4c56fc4-011c-572f-d847-f5c9e4cb923c@gmail.com> (raw)
In-Reply-To: <57afdbe7-4660-ecd0-7d1c-84b59684731f@gmail.com>
On 2/27/23 10:29, Jonathan Yong wrote:
> Attached patch OK?
>
> Excess errors on x86_64-w64-mingw32:
>
> /home/user/p/gcc/src/gcc-git/gcc/testsuite/c-c++-common/Warray-bounds.c:50:3: warning: array subscript 4611686018427387902 is above array bounds of 'struct S16[]' [-Warray-bounds=]
>
> /home/user/p/gcc/src/gcc-git/gcc/testsuite/c-c++-common/Warray-bounds.c:55:3: warning: array subscript 4611686018427387902 is above array bounds of 'struct S16[]' [-Warray-bounds=]
>
> /home/user/p/gcc/src/gcc-git/gcc/testsuite/c-c++-common/Warray-bounds.c:90:3: warning: array subscript 658812288346769699 is above array bounds of 'struct S16[][7]' [-Warray-bounds=]
> gcc/testsuite/ChangeLog:
> * c-c++-common/Warray-bounds.c: Fix excess warnings on
> LLP64.
Ping?
next prev parent reply other threads:[~2023-03-29 4:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 10:29 Jonathan Yong
2023-03-29 4:48 ` Jonathan Yong [this message]
2023-03-31 0:09 ` Mike Stump
2023-03-31 4:09 ` Jonathan Yong
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=a4c56fc4-011c-572f-d847-f5c9e4cb923c@gmail.com \
--to=10walls@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nightstrike@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).