public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/98773] [11 regression] Bootstrap failure: "Trmsgggg" conflicts with declaration
Date: Fri, 22 Jan 2021 10:24:34 +0000	[thread overview]
Message-ID: <bug-98773-4-L54qMkkApA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98773-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Ok, so it's eventually a multilib building (--enable-targets=all) though the
errors sound like frontend errors ...

But if just the tree-data-ref.c hunk is enough to trigger it then it
hints at an issue with

+         if (!tree_fits_shwi_p (CHREC_RIGHT (chrec)))
+           return chrec_dont_know;
+         chrec_right = tree_to_shwi (CHREC_RIGHT (chrec));

which will interpret -1U as -1U instead of -1 for unsigned CHRECs.  It will
treat { 0, +, 255 } (all unsigned char) plain instead of re-interpreting
it as { 0, +, -1 }, maybe that was a wrong "fix".

I have a testcase, -O3 -m32 fails:

char a[128];

void __attribute__((noipa))
foo ()
{
  for (unsigned i = 27; i >= 5; --i)
    a[i] = a[i-5];
}

int main()
{
  __builtin_memcpy (a, "Hello World", sizeof ("Hello World"));
  foo ();
  if (__builtin_memcmp (a + 5, "Hello World", sizeof ("Hello World")) != 0)
    __builtin_abort ();
  return 0;
}

  parent reply	other threads:[~2021-01-22 10:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20 18:55 [Bug ada/98773] New: " ro at gcc dot gnu.org
2021-01-20 18:55 ` [Bug ada/98773] " ro at gcc dot gnu.org
2021-01-20 22:20 ` ro at gcc dot gnu.org
2021-01-21 13:45 ` ro at gcc dot gnu.org
2021-01-22  8:45 ` rguenth at gcc dot gnu.org
2021-01-22  9:34 ` rguenth at gcc dot gnu.org
2021-01-22  9:43 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-01-22 10:24 ` rguenth at gcc dot gnu.org [this message]
2021-01-22 10:30 ` rguenth at gcc dot gnu.org
2021-01-22 10:47 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-01-22 11:50 ` cvs-commit at gcc dot gnu.org
2021-01-22 12:00 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-01-22 12:22 ` marxin at gcc dot gnu.org
2021-01-22 12:31 ` 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-98773-4-L54qMkkApA@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).