public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "liuhongt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/114148] gcc.target/i386/pr106010-7b.c FAILs Date: Fri, 24 May 2024 01:52:02 +0000 [thread overview] Message-ID: <bug-114148-4-IzjkFCQ6mF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114148-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114148 --- Comment #4 from Hongtao Liu <liuhongt at gcc dot gnu.org> --- (In reply to ro@CeBiTec.Uni-Bielefeld.DE from comment #3) > To investigate further, I've added comparison functions to a reduced > version of pr106010-7b.c, with > > void > cmp_epi8 (_Complex unsigned char* a, _Complex unsigned char* b) > { > for (int i = 0; i != N; i++) > if (a[i] != b[i]) > { > printf ("cmp_epi8: i = %d: a[i].r = %x a[i].i = %x b[i].r = %x b[i].i = > %x\n", > i, __real__ a[i], __imag__ a[i], __real__ b[i], __imag__ b[i]); > } > } > > This shows (when using _Complex unsigned char since on Solaris, char is > signed by default) > > cmp_epi8: i = 76: a[i].r = 0 a[i].i = 0 b[i].r = 88 b[i].i = 33 > cmp_epi8: i = 77: a[i].r = 0 a[i].i = 0 b[i].r = 6 b[i].i = 8 > cmp_epi8: i = 80: a[i].r = 0 a[i].i = 0 b[i].r = 3 b[i].i = 0 > > I've also noticed that the test result depends on the implementation of > malloc used: > > * With Solaris libc malloc, libmalloc, and watchmalloc, the test aborts. > > * However, when using one of libbsdmalloc, libmapmalloc, libmtmalloc, or > libumem, the test works. > > However, ISTM that the test is simply bogus: in avx_test > > * epi8_src, epi8_dst are allocated with malloc, buffer contents undefined > > * epi8_dst is cleared > > * epi8_dst is initialized from p_init > > * in foo_epi8, epi8_src[0] (an undefined value) is copied into first N > elements of epi8_dst > > * epi8_dst is compared to epi8_src (with the remaining members of epi8_src > still undefined) uoops, does below patch fix the testcase on Solaris/x86? memcpy (pd_src, p_init, 2 * N * sizeof (double)); - memcpy (ps_dst, p_init, 2 * N * sizeof (float)); - memcpy (epi64_dst, p_init, 2 * N * sizeof (long long)); - memcpy (epi32_dst, p_init, 2 * N * sizeof (int)); - memcpy (epi16_dst, p_init, 2 * N * sizeof (short)); - memcpy (epi8_dst, p_init, 2 * N * sizeof (char)); + memcpy (ps_src, p_init, 2 * N * sizeof (float)); + memcpy (epi64_src, p_init, 2 * N * sizeof (long long)); + memcpy (epi32_src, p_init, 2 * N * sizeof (int)); + memcpy (epi16_src, p_init, 2 * N * sizeof (short)); + memcpy (epi8_src, p_init, 2 * N * sizeof (char)); > > Why on earth would the rest of epi8_dst and epi8_src be identical if > epi8_src was never initialized? Guess, epi8_src is all zero, and epi8_dst if set as epi8_src[0] by foo_epi8.
next prev parent reply other threads:[~2024-05-24 1:52 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-28 12:46 [Bug target/114148] New: " ro at gcc dot gnu.org 2024-02-28 12:47 ` [Bug target/114148] " ro at gcc dot gnu.org 2024-02-28 12:48 ` ro at gcc dot gnu.org 2024-05-23 12:27 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-05-24 1:52 ` liuhongt at gcc dot gnu.org [this message] 2024-05-24 7:47 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-05-24 7:51 ` cvs-commit at gcc dot gnu.org 2024-05-24 7:52 ` liuhongt 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-114148-4-IzjkFCQ6mF@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: linkBe 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).