From: "Thomas Preud'homme" <thomas.preudhomme@arm.com>
To: "'Christophe Lyon'" <christophe.lyon@linaro.org>
Cc: "GCC Patches" <gcc-patches@gcc.gnu.org>
Subject: RE: [PATCH] Fix PR63266: Keep track of impact of sign extension in bswap
Date: Wed, 22 Oct 2014 08:57:00 -0000 [thread overview]
Message-ID: <000701cfedd6$1754ee60$45fecb20$@arm.com> (raw)
In-Reply-To: <CAKdteObxtNKVc-3H_3LRLCOZxKz0buNWfioC8SpTaUYxmA93NQ@mail.gmail.com>
> From: Christophe Lyon [mailto:christophe.lyon@linaro.org]
> Sent: Tuesday, October 21, 2014 10:03 PM
> > +typedef int SItype __attribute__ ((mode (SI)));
> What's the purpose of this? It seems unused.
Sigh. Bad copy/paste from optimize-bswapsi-1.c
I'll add it to my patch for pr63259.
> I believe this should be:
> "checks that unknown byte markers are set correctly in case of cast"
Indeed, there is a 's' missing for markers.
>
> > +
> > +HItype
> > +swap16 (HItype in)
> > +{
> > + return (HItype) (((in >> 0) & 0xFF) << 8)
> > + | (((in >> 8) & 0xFF) << 0);
> > +}
> > +
> > /* { dg-final { scan-tree-dump-times "16 bit load in target endianness
> found at" 3 "bswap" } } */
> > -/* { dg-final { scan-tree-dump-times "16 bit bswap implementation
> found at" 3 "bswap" { xfail alpha*-*-* arm*-*-* } } } */
> > +/* { dg-final { scan-tree-dump-times "16 bit bswap implementation
> found at" 1 "bswap" { target alpha*-*-* arm*-*-* } } } */
>
> This line fails when forcing the compiler to target -march=armv5t for
> instance. I suspect this is because the check_effective_target_bswap
> test is too permissive.
Yep, it's likely to be the case. Feel to add a version check in it.
Thanks for the review.
Best regards,
Thomas
next prev parent reply other threads:[~2014-10-22 8:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 10:27 Thomas Preud'homme
2014-09-24 1:57 ` Thomas Preud'homme
2014-09-24 8:01 ` Richard Biener
2014-09-24 20:27 ` Christophe Lyon
2014-09-25 6:41 ` Thomas Preud'homme
2014-09-25 14:08 ` Christophe Lyon
2014-09-26 2:27 ` Thomas Preud'homme
2014-09-26 16:12 ` Christophe Lyon
2014-10-21 9:30 ` Thomas Preud'homme
2014-10-21 11:50 ` Richard Biener
2014-10-21 21:06 ` Christophe Lyon
2014-10-22 8:57 ` Thomas Preud'homme [this message]
2014-10-26 16:50 ` Christophe Lyon
2014-10-27 12:16 ` Thomas Preud'homme
2014-10-28 12:28 ` [PATCH] Fix up " Jakub Jelinek
2014-10-28 13:00 ` Richard Biener
2014-10-29 9:36 ` Thomas Preud'homme
2014-10-29 9:40 ` Thomas Preud'homme
2014-10-29 9:43 ` Jakub Jelinek
2014-10-29 10:37 ` Thomas Preud'homme
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='000701cfedd6$1754ee60$45fecb20$@arm.com' \
--to=thomas.preudhomme@arm.com \
--cc=christophe.lyon@linaro.org \
--cc=gcc-patches@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).