public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave.anglin at bell dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/106480] FAIL: gcc.dg/Warray-bounds-48.c pr102706 (test for warnings, line 33)
Date: Mon, 01 Aug 2022 11:46:36 +0000 [thread overview]
Message-ID: <bug-106480-4-8ao3dhZSiF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106480-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106480
--- Comment #2 from dave.anglin at bell dot net ---
On 2022-08-01 5:12 a.m., rguenth at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106480
>
> Richard Biener <rguenth at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Keywords| |testsuite-fail
>
> --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
> Both are guarded like
>
> p->a0[0] = 4; p->a0[1] = 5; // { dg-warning "\\\[-Wstringop-overflow"
> "pr102706" { target { vect_slp_v2hi_store_align && { !
> vect_slp_v4hi_store_unalign } } } }
>
> the vect_slp_* predicates according to comments implement exactly the case in
> the testsuite, but for some reason it doesn't work on hppa?
Yes, I guess this implies a problem with
# Return the true if target support vectorization of 4-byte short stores
# with 4-byte aligned address at plain O2.
proc check_effective_target_vect_slp_v2hi_store_align { } {
set pattern {add new stmt: MEM <vector\(2\) short int>}
set macro "TEST_V2HI_2"
return [check_cached_effective_target vect_slp_v2hi_store_align {
expr [check_vect_slp_store_usage $pattern $macro ] }]
}
# Return the true if target support vectorization of 8-byte short stores
# with unaligned address at plain O2.
# NB: This target should be removed after real issues are fixed for
# -Wstringop-overflow with O2 vect. Be careful if you want to reuse
# this target since tests in check_vect_slp_store_usage
# is the exact match of relative testcases
proc check_effective_target_vect_slp_v4hi_store_unalign { } {
set pattern {add new stmt: MEM <vector\(4\) short int>}
set macro "TEST_V4HI"
return [check_cached_effective_target vect_slp_v4hi_store_unalign {
expr [check_vect_slp_store_usage $pattern $macro ] }]
}
in target-supports.exp.
prev parent reply other threads:[~2022-08-01 11:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 17:43 [Bug tree-optimization/106480] New: " danglin at gcc dot gnu.org
2022-08-01 9:12 ` [Bug tree-optimization/106480] " rguenth at gcc dot gnu.org
2022-08-01 11:46 ` dave.anglin at bell dot net [this message]
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-106480-4-8ao3dhZSiF@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).