public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/90806] Warray-bounds-2.c fail on cross-aarch64 on RH6 host
Date: Mon, 04 Jan 2021 09:39:01 +0000	[thread overview]
Message-ID: <bug-90806-4-zodSjj5zpc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-90806-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from rguenther at suse dot de <rguenther at suse dot de> ---
On Mon, 4 Jan 2021, ebotcazou at gcc dot gnu.org wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90806
> 
> --- Comment #10 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> > Since -9223372036854775808 is 0x8000000000000000 and ar3[0] == 1 it suggests
> > that the offset is somewhere truncated to 32bits ... but I can't reproduce
> > with a x86_64 to aarch64 cross and your reduced testcase for example.
> 
> I should have said that this is for a native x86-64/Linux GCC 10 compiler: if
> you compile it with GCC 9 or with GCC 10, then the FRE1 pass behaves
> differently

So you say that a not bootstrapped GCC 10 compiler compiled with
a recent host GCC 11 compiler folds to 1 while using a host GCC 10 (or 9)
compiler does not fold to 1?

My dev build of GCC 10 head (using GCC 7 as host compiler does not
fold to 1)

  parent reply	other threads:[~2021-01-04  9:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-90806-4@http.gcc.gnu.org/bugzilla/>
2020-12-14 21:00 ` ebotcazou at gcc dot gnu.org
2021-01-04  8:14 ` rguenth at gcc dot gnu.org
2021-01-04  8:34 ` ebotcazou at gcc dot gnu.org
2021-01-04  9:39 ` rguenther at suse dot de [this message]
2021-01-05  9:36 ` ebotcazou at gcc dot gnu.org
2021-01-06  9:36 ` ebotcazou at gcc dot gnu.org
2021-01-06  9:56 ` ebotcazou at gcc dot gnu.org
2021-01-06 10:00 ` rguenth at gcc dot gnu.org
2021-01-06 10:09 ` ebotcazou at gcc dot gnu.org
2021-01-06 10:19 ` rguenther at suse dot de
2021-01-06 11:13 ` cvs-commit at gcc dot gnu.org
2021-01-06 11:15 ` ebotcazou 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-90806-4-zodSjj5zpc@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).