fix Issue 19662 - x86_64: Different code output when compiling with i…

[WalterBright]

…nline/boundscheck on/off

The test case from bugzilla works for me, let's see how it does in the test suite.

[dlang-bot]

Thanks for your pull request, @WalterBright!

Bugzilla references

Auto-close	Bugzilla	Severity	Description
✓	19662	major	x86_64: Different code output when compiling with inline/boundscheck on/off

Testing this PR locally

If you don't have a local development environment setup, you can use Digger to test this PR:

dub run digger -- build "master + dmd#11944"

[thewilsonator]

Seems to be specifically windows x64.

[WalterBright]

Can someone email me the object file it generates for one of the failed runs of test19662.d ?

[thewilsonator]

sorry my windows box is out of commission. Easiest way is probably to set up DMD as a cross complier by hardcoding

enum TARGET : bool
{
    Linux        = xversion!`linux`,
    OSX          = xversion!`OSX`,
    FreeBSD      = xversion!`FreeBSD`,
    OpenBSD      = xversion!`OpenBSD`,
    Solaris      = xversion!`Solaris`,
    Windows      = xversion!`Windows`,
    DragonFlyBSD = xversion!`DragonFlyBSD`,
}

in globals.d to be

enum TARGET : bool
{
    Linux        = false,
    OSX          = false,
    FreeBSD      = false,
    OpenBSD      = false,
    Solaris      = false,
    Windows      = true,
    DragonFlyBSD = false,
}

[MoonlightSentinel]

Can someone email me the object file it generates for one of the failed runs of test19662.d ?

test19662.zip

[Geod24]

Any update on this @WalterBright ?

[RazvanN7]

@WalterBright what is the status of this PR?

[ibuclaw]

Wrong test directory. Build is still broken.