public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "herumi at nifty dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/104603] [10/11/12 Regression] wrong detection of  -Warray-bounds for interesting tail resusive case
Date: Sat, 19 Feb 2022 06:48:21 +0000	[thread overview]
Message-ID: <bug-104603-4-Baik7g5ozb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104603-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104603

--- Comment #5 from herumi <herumi at nifty dot com> ---

>Can you file a seperate issue with the preprocessed source (-save-temps) since it really does look like a seperate issue all together.

May I attach a zipped a.ii which is generated by the following commands?
The size of a.ii is over 1700KiB.

---
>cat a.cpp
#include <xbyak/xbyak.h>

using namespace Xbyak::util;

void f()
{
  ptr[eax] == ptr[eax];
}
---
---
g++-11.2 -O2 -I ../ -Warray-bounds -c a.cpp -save-temps
---

  parent reply	other threads:[~2022-02-19  6:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-19  5:21 [Bug c++/104603] New: wrong detection of g++ -Warray-bounds about downcast herumi at nifty dot com
2022-02-19  5:46 ` [Bug c++/104603] " pinskia at gcc dot gnu.org
2022-02-19  5:51 ` [Bug tree-optimization/104603] [10/11/12 Regression] wrong detection of -Warray-bounds for interesting tail resusive case pinskia at gcc dot gnu.org
2022-02-19  6:15 ` herumi at nifty dot com
2022-02-19  6:22 ` pinskia at gcc dot gnu.org
2022-02-19  6:48 ` herumi at nifty dot com [this message]
2022-02-19  6:53 ` pinskia at gcc dot gnu.org
2022-02-19  7:40 ` herumi at nifty dot com
2022-03-01 20:51 ` msebor at gcc dot gnu.org
2022-03-09 13:03 ` rguenth at gcc dot gnu.org
2022-06-28 10:48 ` [Bug tree-optimization/104603] [10/11/12/13 " jakub at gcc dot gnu.org
2023-07-07 10:42 ` [Bug tree-optimization/104603] [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-104603-4-Baik7g5ozb@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: 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).