public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/102946] [12 Regression] gcc.dg/vect/pr101145_1.c etc. FAIL
Date: Wed, 27 Oct 2021 09:41:17 +0000 [thread overview]
Message-ID: <bug-102946-4-sj7dTp2PVi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102946-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102946
--- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
> Very likely might be fixed with properly aligning the data like with adding
>
> a = __builtin_assume_aligned (a, __BIGGEST_ALIGNMENT__);
> b = __builtin_assume_aligned (b, __BIGGEST_ALIGNMENT__);
>
> at the top of each function in pr101145.inc - note the global variables
> would then need a similar aligned attribute for correctness.
>
> Rainer, if you can manage to test this and that works such change is
> pre-approved.
While this fixes the 64-bit SPARC case, the 32-bit failures remain.
pr101145_1.c dump attached.
next prev parent reply other threads:[~2021-10-27 9:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 14:33 [Bug testsuite/102946] New: " ro at gcc dot gnu.org
2021-10-26 14:34 ` [Bug testsuite/102946] " ro at gcc dot gnu.org
2021-10-26 14:35 ` ro at gcc dot gnu.org
2021-10-26 14:36 ` ro at gcc dot gnu.org
2021-10-27 6:45 ` [Bug testsuite/102946] [12 Regression] " rguenth at gcc dot gnu.org
2021-10-27 9:41 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2021-10-27 9:42 ` ro at gcc dot gnu.org
2021-10-28 1:54 ` guojiufu at gcc dot gnu.org
2021-12-16 1:52 ` guojiufu 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-102946-4-sj7dTp2PVi@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).