public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/94675] [9/10 regression] -Warray-bounds false positive with -O2 since r9-1948 Date: Fri, 24 Apr 2020 15:16:23 +0000 [thread overview] Message-ID: <bug-94675-4-vau7UflVG9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94675-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94675 --- Comment #17 from Martin Sebor <msebor at gcc dot gnu.org> --- As you observed, the warning disappears if the assert is removed, so that's one workaround. But rather than working around it I would suggest to rewrite the code to avoid the pointer subtraction. Chances are it will not only avoid the warning but help improve the emitted object code. I'm not sure I understand correctly what the test case is meant to do but the example below shows what I'm thinking of. If modifying the code isn't feasible then #pragma GCC diagnostic is the recommended suppression mechanism. typedef unsigned char byte; typedef __PTRDIFF_TYPE__ ptrdiff_t; typedef __SIZE_TYPE__ size_t; typedef struct pstream_t { const byte * p; ptrdiff_t n; } pstream_t; static inline _Bool ps_has (const pstream_t *ps, size_t len) { return (size_t)ps->n >= len; } static inline int __ps_skip (pstream_t * ps, size_t len) { if (!ps_has (ps, len)) __builtin_abort (); ps->p += len; ps->n -= len; return 0; } static inline int ps_skip (pstream_t * ps, size_t len) { return ps_has (ps, len) ? __ps_skip(ps, len) : -1; } byte c; int c_len; void f(void) { pstream_t ps = { &c, c_len }; ps_skip (&ps, 7); }
next prev parent reply other threads:[~2020-04-24 15:16 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-20 19:42 [Bug tree-optimization/94675] New: [9 regression] -Warray-bounds false positive with -O2 chantry.xavier at gmail dot com 2020-04-20 22:16 ` [Bug tree-optimization/94675] " msebor at gcc dot gnu.org 2020-04-21 6:51 ` chantry.xavier at gmail dot com 2020-04-21 7:04 ` marxin at gcc dot gnu.org 2020-04-21 7:46 ` rguenth at gcc dot gnu.org 2020-04-21 7:58 ` [Bug tree-optimization/94675] [9/10 " rguenth at gcc dot gnu.org 2020-04-21 7:59 ` jakub at gcc dot gnu.org 2020-04-21 8:06 ` [Bug tree-optimization/94675] [9/10 regression] -Warray-bounds false positive with -O2 since r9-1948 jakub at gcc dot gnu.org 2020-04-21 14:03 ` law at redhat dot com 2020-04-21 14:18 ` rguenther at suse dot de 2020-04-21 14:43 ` law at redhat dot com 2020-04-21 14:57 ` rguenther at suse dot de 2020-04-21 14:58 ` msebor at gcc dot gnu.org 2020-04-21 19:14 ` law at redhat dot com 2020-04-21 19:16 ` law at redhat dot com 2020-04-21 20:10 ` law at redhat dot com 2020-04-21 21:00 ` msebor at gcc dot gnu.org 2020-04-22 6:34 ` rguenther at suse dot de 2020-04-24 7:48 ` chantry.xavier at gmail dot com 2020-04-24 15:16 ` msebor at gcc dot gnu.org [this message] 2020-04-30 13:12 ` chantry.xavier at gmail dot com 2021-06-01 8:17 ` [Bug tree-optimization/94675] [9/10/11/12 " rguenth at gcc dot gnu.org 2021-09-06 11:25 ` pinskia at gcc dot gnu.org 2022-03-16 11:09 ` chantry.xavier at gmail dot com 2022-03-16 13:24 ` rguenth at gcc dot gnu.org 2022-05-27 9:42 ` [Bug tree-optimization/94675] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:40 ` jakub at gcc dot gnu.org 2023-05-14 21:25 ` [Bug tree-optimization/94675] [10/11/12/13/14 " pinskia at gcc dot gnu.org 2023-07-07 10:37 ` [Bug tree-optimization/94675] [11/12/13/14 " rguenth 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-94675-4-vau7UflVG9@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: linkBe 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).