From: Iain Sandoe <iain@sandoe.co.uk>
To: Martin Sebor <msebor@gmail.com>
Cc: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>, GCC-patches@gcc.gnu.org
Subject: Re: committed] correct memcmp expansion of constant representations containing embedded nuls (PR 95189)
Date: Wed, 22 Jul 2020 09:36:40 +0100 [thread overview]
Message-ID: <7CA32E30-1C8F-400F-AC1C-EFA93EC8EB07@sandoe.co.uk> (raw)
In-Reply-To: <yddzh7s7yc8.fsf@CeBiTec.Uni-Bielefeld.DE>
Hi Martin,
Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> wrote:
>>
>> I have committed this change in r11-2231 after Jeff approved it
>> off list last Thursday.
>
> the new gcc.target/i386/memcpy-pr95886.c test FAILs on 32-bit x86
> (i386-pc-solaris2.11):
>
> +FAIL: gcc.target/i386/memcpy-pr95886.c scan-rtl-dump-times expand
> "const_int 1976943448883713" 1
> +FAIL: gcc.target/i386/memcpy-pr95886.c scan-rtl-dump-times expand
> "const_int 576467370915332609" 1
> +FAIL: gcc.target/i386/memcpy-pr95886.c scan-rtl-dump-times expand
> "const_int 578431098682540545" 1
> +FAIL: gcc.target/i386/memcpy-pr95886.c scan-rtl-dump-times expand
> "const_int 578437695685198337" 1
> +FAIL: gcc.target/i386/memcpy-pr95886.c scan-rtl-dump-times expand
> "const_int 578437695685198337" 1
> +FAIL: gcc.target/i386/memcpy-pr95886.c scan-rtl-dump-times expand
> "const_int 578437695752110593" 1
> +FAIL: gcc.target/i386/memcpy-pr95886.c scan-rtl-dump-times expand
> "const_int 578437695752306689" 1
> +FAIL: gcc.target/i386/memcpy-pr95886.c scan-rtl-dump-times expand
> "const_int 578437695752307200" 1
> +FAIL: gcc.target/i386/memcpy-pr95886.c scan-rtl-dump-times expand
> "const_int 578437695752307201” 2
likewise, the tests fail on m32 Darwin,
thanks
Iain
next prev parent reply other threads:[~2020-07-22 8:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 0:23 [PATCH] " Martin Sebor
2020-07-07 20:02 ` Martin Sebor
2020-07-14 0:06 ` [PING #2][PATCH] " Martin Sebor
2020-07-20 18:43 ` committed] " Martin Sebor
2020-07-22 8:23 ` Rainer Orth
2020-07-22 8:36 ` Iain Sandoe [this message]
2020-07-23 20:12 ` Martin Sebor
2020-07-23 20:18 ` H.J. Lu
2020-07-23 23:50 ` Martin Sebor
2020-07-24 2:26 ` H.J. Lu
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=7CA32E30-1C8F-400F-AC1C-EFA93EC8EB07@sandoe.co.uk \
--to=iain@sandoe.co.uk \
--cc=GCC-patches@gcc.gnu.org \
--cc=msebor@gmail.com \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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).