public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "guojiufu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/102072] New test case gcc.dg/vect/pr101145_3.c in r12-3136 fails on armeb
Date: Thu, 26 Aug 2021 14:27:38 +0000	[thread overview]
Message-ID: <bug-102072-4-WvxE4AIq9e@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102072-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Jiu Fu Guo <guojiufu at gcc dot gnu.org> ---
Code around tree-ssa-loop-manip.c:1049 (in determine_exit_conditions) is:
  else if (cmp == GT_EXPR)
    {
      gcc_assert (tree_int_cst_sign_bit (step));
    }

which seems checking: 'step' should be negative if 'cmp' is ">"

code around pr101145.c:6 :
  5unsigned __attribute__ ((noinline))
  6foo (int *__restrict__ a, int *__restrict__ b, unsigned l, unsigned n)
  7{
  8  while (n < ++l)
  9    *a++ = *b++ + 1;
 10  return l;
 11}

------------
I did not find arm big-endian yet, I'm trying to reproduce this issue on other
targets...

  parent reply	other threads:[~2021-08-26 14:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26  8:39 [Bug target/102072] New: " clyon at gcc dot gnu.org
2021-08-26  9:58 ` [Bug tree-optimization/102072] " rguenth at gcc dot gnu.org
2021-08-26 11:20 ` rearnsha at gcc dot gnu.org
2021-08-26 12:47 ` clyon at gcc dot gnu.org
2021-08-26 14:27 ` guojiufu at gcc dot gnu.org [this message]
2021-08-26 14:39 ` rearnsha at gcc dot gnu.org
2021-08-27  6:44 ` guojiufu at gcc dot gnu.org
2021-08-27  9:00 ` guojiufu at gcc dot gnu.org
2021-08-27 10:04 ` guojiufu at gcc dot gnu.org
2021-08-27 12:53 ` hjl.tools at gmail dot com

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-102072-4-WvxE4AIq9e@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).