public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dongjianqiang2 at huawei dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/100499] Different results with -fpeel-loops -ftree-loop-vectorize options
Date: Tue, 11 May 2021 09:12:55 +0000	[thread overview]
Message-ID: <bug-100499-4-BOjTIRLyB8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100499-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from John Dong <dongjianqiang2 at huawei dot com> ---
(In reply to Martin Liška from comment #3)
> But expected result is end g_2823 = 32768, right?
> Clang returns the same result 32768.

Yes, I think so.

  parent reply	other threads:[~2021-05-11  9:12 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10 10:20 [Bug tree-optimization/100499] New: " dongjianqiang2 at huawei dot com
2021-05-10 11:13 ` [Bug tree-optimization/100499] " rguenth at gcc dot gnu.org
2021-05-11  9:06 ` marxin at gcc dot gnu.org
2021-05-11  9:07 ` marxin at gcc dot gnu.org
2021-05-11  9:09 ` marxin at gcc dot gnu.org
2021-05-11  9:12 ` dongjianqiang2 at huawei dot com [this message]
2021-05-11  9:42 ` rguenth at gcc dot gnu.org
2021-05-11 10:40 ` amker at gcc dot gnu.org
2021-05-11 11:33 ` marxin at gcc dot gnu.org
2021-05-17  2:17 ` amker at gcc dot gnu.org
2021-05-18  9:49 ` rguenth at gcc dot gnu.org
2021-05-18  9:57 ` rguenth at gcc dot gnu.org
2021-05-18 10:25 ` rguenth at gcc dot gnu.org
2021-05-18 11:33 ` amker at gcc dot gnu.org
2021-05-18 11:36 ` amker at gcc dot gnu.org
2021-05-18 11:54 ` rguenther at suse dot de
2021-05-18 15:46 ` amacleod at redhat dot com
2021-05-19  6:31 ` rguenth at gcc dot gnu.org
2021-05-19  7:10 ` amker at gcc dot gnu.org
2021-05-19  7:15 ` amker at gcc dot gnu.org
2021-05-19  8:24 ` aldyh at redhat dot com
2021-05-19 18:11 ` amacleod at redhat dot com
2021-05-22 15:37 ` law at gcc dot gnu.org
2021-05-26  8:14 ` aldyh at gcc dot gnu.org
2021-05-26  8:21 ` aldyh at gcc dot gnu.org
2021-05-26  8:34 ` rguenther at suse dot de
2021-05-26  8:40 ` aldyh at redhat dot com
2021-05-26  8:59 ` rguenther at suse dot de
2021-05-26 13:17 ` amacleod at redhat dot com
2021-05-26 13:23 ` rguenther at suse dot de
2021-05-26 13:30 ` aldyh at redhat dot com
2021-07-22  8:09 ` [Bug tree-optimization/100499] [9/10/11/12 Regression] " rguenth at gcc dot gnu.org
2021-07-22  8:09 ` rguenth at gcc dot gnu.org
2021-07-22  8:11 ` rguenth at gcc dot gnu.org
2021-07-28  9:05 ` rguenth at gcc dot gnu.org
2021-07-29  7:56 ` ebotcazou at gcc dot gnu.org
2022-01-24 13:16 ` rguenth at gcc dot gnu.org
2022-01-24 13:16 ` rguenth at gcc dot gnu.org
2022-01-24 13:17 ` rguenth at gcc dot gnu.org
2022-01-31  8:08 ` cvs-commit at gcc dot gnu.org
2022-01-31  8:38 ` cvs-commit at gcc dot gnu.org
2022-02-04 13:39 ` cvs-commit at gcc dot gnu.org
2022-02-04 13:40 ` [Bug tree-optimization/100499] [9/10/11 " rguenth at gcc dot gnu.org
2022-02-15 12:23 ` rguenth at gcc dot gnu.org
2022-05-27  9:45 ` [Bug tree-optimization/100499] [10/11 " rguenth at gcc dot gnu.org
2022-06-28 10:44 ` jakub at gcc dot gnu.org
2023-07-07 10:39 ` [Bug tree-optimization/100499] [11 " 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-100499-4-BOjTIRLyB8@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).