From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Martin Sebor <msebor@gmail.com>
Cc: Prathamesh Kulkarni <prathamesh.kulkarni@linaro.org>,
Christophe Lyon <christophe.lyon@linaro.org>,
gcc Patches <gcc-patches@gcc.gnu.org>,
Kyrill Tkachov <kyrylo.tkachov@arm.com>
Subject: Re: PR81703 and Martin's fix for PR83501
Date: Thu, 11 Jan 2018 21:59:00 -0000 [thread overview]
Message-ID: <ydd1siwrrr3.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <94c15f57-5bfe-a66a-712a-cc74a4f6f209@gmail.com> (Martin Sebor's message of "Thu, 11 Jan 2018 09:33:36 -0700")
Hi Martin,
>> I am not sure why constant string is not emitted for arm-linux-gnueabihf ?
>> As far as this issue is concerned, should I simply XFAIL it on arm for now ?
>
> This is not unique to the arm back end but affects other targets
> as well, including powerpc64. There's a bug open (PR 83462) for
> one of the tests I recently added with the same root cause:
> a case not being handled by the strlen pass. I'm tracking this
> missed optimization in PR 83543. I would expect handling it
> to be fairly easy but it seems that every I think that it turns
> out to be anything but. Either way, either fixing 83543 or
> marking this failure (and those in PR 83462) XFAIL until it
> the optimization is added should work.
I'm seeing the same failure on sparc*-sun-solaris*, and gcc-testresults
shows it on mips64el-unknown-linux-gnu and powerpc-ibm-aix7.2.0.0, too.
XFAILing may become unwieldly if more targets are affected.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2018-01-11 21:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 18:46 Prathamesh Kulkarni
2018-01-10 21:40 ` Jeff Law
2018-01-11 9:22 ` Christophe Lyon
2018-01-11 10:58 ` Prathamesh Kulkarni
2018-01-11 12:07 ` Prathamesh Kulkarni
2018-01-11 16:56 ` Martin Sebor
2018-01-11 21:59 ` Rainer Orth [this message]
2018-01-12 6:41 ` Martin Sebor
2018-01-12 6:46 ` Prathamesh Kulkarni
2018-01-12 16:28 ` Martin Sebor
2018-01-12 17:46 ` Jeff Law
2018-01-12 17:56 ` Jakub Jelinek
2018-01-14 9:42 ` Prathamesh Kulkarni
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=ydd1siwrrr3.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=christophe.lyon@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=kyrylo.tkachov@arm.com \
--cc=msebor@gmail.com \
--cc=prathamesh.kulkarni@linaro.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).