From: Ulf Magnusson <ulfalizer@gmail.com>
To: gcc@gcc.gnu.org
Subject: Re: Option to make unsigned->signed conversion always well-defined?
Date: Thu, 06 Oct 2011 08:25:00 -0000 [thread overview]
Message-ID: <CAFkk2KSZzupdJt-qB7VLJishN4kjE1BZWFqrpajw1MXcfv-a+w@mail.gmail.com> (raw)
In-Reply-To: <CAFkk2KSn2Us=W2ER396pA+cbgW1HaTJWb-mLPiJVv4Xk0QJYuA@mail.gmail.com>
On Wed, Oct 5, 2011 at 10:11 PM, Ulf Magnusson <ulfalizer@gmail.com> wrote:
> Hi,
>
> I've been experimenting with different methods for emulating the
> signed overflow of an 8-bit CPU. The method I've found that seems to
> generate the most efficient code on both ARM and x86 is
>
> bool overflow(unsigned int a, unsigned int b) {
> const unsigned int sum = (int8_t)a + (int8_t)b;
> return (int8_t)sum != sum;
> }
>
> (The real function would probably be 'inline', of course. Regs are
> stored in overlong variables, hence 'unsigned int'.)
>
> Looking at the spec, it unfortunately seems the behavior of this
> function is undefined, as it relies on signed int addition wrapping,
> and that (int8_t)sum truncates bits. Is there some way to make this
> guaranteed safe with GCC without resorting to inline asm? Locally
> enabling -fwrap takes care of the addition, but that still leaves the
> conversion.
>
> /Ulf
>
Is *((int8_t*)&sum) safe (assuming little endian)? Unfortunately that
seems to generate worse code. On X86 it generates the following (GCC
4.5.2):
00000050 <_Z9overflow4jj>:
50: 83 ec 10 sub $0x10,%esp
53: 0f be 54 24 18 movsbl 0x18(%esp),%edx
58: 0f be 44 24 14 movsbl 0x14(%esp),%eax
5d: 8d 04 02 lea (%edx,%eax,1),%eax
60: 0f be d0 movsbl %al,%edx
63: 39 d0 cmp %edx,%eax
65: 0f 95 c0 setne %al
68: 83 c4 10 add $0x10,%esp
6b: c3 ret
With the straight (int8_t) cast you get
50: 0f be 54 24 08 movsbl 0x8(%esp),%edx
55: 0f be 44 24 04 movsbl 0x4(%esp),%eax
5a: 8d 04 02 lea (%edx,%eax,1),%eax
5d: 0f be d0 movsbl %al,%edx
60: 39 c2 cmp %eax,%edx
62: 0f 95 c0 setne %al
65: c3 ret
What's with the extra add/sub of ESP?
/Ulf
next prev parent reply other threads:[~2011-10-05 20:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 22:56 Ulf Magnusson
2011-10-06 8:25 ` Ulf Magnusson [this message]
2011-10-06 9:04 ` Pedro Pedruzzi
2011-10-06 10:52 ` Ulf Magnusson
2011-10-06 14:42 ` Ulf Magnusson
2011-10-06 14:45 ` Miles Bader
2011-10-06 14:48 ` Ulf Magnusson
2011-10-06 21:31 ` Pedro Pedruzzi
2011-10-07 11:52 ` Miles Bader
2011-10-07 17:20 ` Pedro Pedruzzi
2011-10-07 17:35 ` Miles Bader
[not found] ` <4E8DBF3C.1020700@redhat.com>
2011-10-06 22:08 ` Ulf Magnusson
2011-10-06 22:46 ` Florian Weimer
2011-10-07 19:36 ` Ulf Magnusson
2011-10-07 22:24 ` Florian Weimer
2011-10-07 22:48 ` Ulf Magnusson
2011-10-07 23:36 ` Florian Weimer
2011-10-06 18:24 Jeremy Hall
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=CAFkk2KSZzupdJt-qB7VLJishN4kjE1BZWFqrpajw1MXcfv-a+w@mail.gmail.com \
--to=ulfalizer@gmail.com \
--cc=gcc@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).