On Sun, Jul 10, 2016 at 7:34 PM, Yasushi SHOJI <yasushi.shoji@gmail.com>
wrote:
> On Thu, Jul 7, 2016 at 12:04 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > So more data points might help, yes.
>
> I can reproduce this bug on my Debian Sid system with
> gcc version 5.4.0 20160609 (Debian 5.4.0-6).

I should have tested with different compilers before posting the
previous comment since Eli predicted that a bad compiler is a problem.

Yes, the results differ depending on the compiler you use.

Here is the results:

 - All test is done with 7bf54d0 + the previous patch applied
 - no option to configure except specifying compiler with CC=

| gcc 6   | good | 6.1.1 20160705 (Debian 6.1.1-9) |
| gcc 5   | bad  | 5.4.0 20160609 (Debian 5.4.0-6) |
| gcc 4.9 | good | 4.9.3 (Debian 4.9.3-14)         |
| gcc 4.8 | good | 4.8.5 (Debian 4.8.5-4)          |

  - good: returns 10
  - bad: returns 20

So the current default compiler on Debian Sid is the one to create a
bad binary with the current source code.

Let me know if you need any other info.
-- 
           yashi