On Thu, Apr 2, 2020 at 12:47 PM Philippe Mathieu-Daudé <phi...@redhat.com> wrote:
> Cc'ing the persons referenced in the commit you referred, > who happened to be chatting about this issue few hours ago on IRC. > > Thanks, adding --disable-pie to configure solves this issue, but I guess the default detection should work ;-) Best, Howard > On 4/2/20 11:28 AM, Howard Spoelstra wrote: > > Hi, > > > > I just compiled qemu-system-ppc for Windows, using native msys2 on > > Windows 10 64 bit and the 64 bit mingw cross compiler on Fedora 31. Both > > create executables that crash: > > > > qemu-system-ppc.exe -L pc-bios -boot c -m 512 -M mac99,via=pmu -h > > da C:\Mac-disks\9.2.img > > Exception code=0xc0000005 flags=0x0 at 0x00007FFB2A602078. Access > > violation - attempting to write data at address 0x00000000034C76EC > > > > I bisected this down to: > > > > d2cd29e30736afd4a1e8cac3cf4da360bbc65978 is the first bad commit > > commit d2cd29e30736afd4a1e8cac3cf4da360bbc65978 > > Author: Richard Henderson <richard.hender...@linaro.org > > <mailto:richard.hender...@linaro.org>> > > Date: Tue Dec 17 13:47:37 2019 -1000 > > > > configure: Do not force pie=no for non-x86 > > > > PIE is supported on many other hosts besides x86. > > > > The default for non-x86 is now the same as x86: pie is used > > if supported, and may be forced via --enable/--disable-pie. > > > > The original commit (40d6444e91c) said: > > > > "Non-x86 are not changed, as they require TCG changes" > > > > but I think that's wrong -- there's nothing about PIE that > > affects TCG one way or another. > > > > Tested on aarch64 (bionic) and ppc64le (centos 7) hosts. > > > > Tested-by: Alex Bennée <alex.ben...@linaro.org > > <mailto:alex.ben...@linaro.org>> > > Reviewed-by: Alex Bennée <alex.ben...@linaro.org > > <mailto:alex.ben...@linaro.org>> > > Reviewed-by: Philippe Mathieu-Daudé <phi...@redhat.com > > <mailto:phi...@redhat.com>> > > Signed-off-by: Richard Henderson <richard.hender...@linaro.org > > <mailto:richard.hender...@linaro.org>> > > > > Please note that I tried again after applying patch > > https://patchwork.ozlabs.org/patch/1265368/ However, this has not > solved > > my issue. > > > > Best, > > Howard > > > > > >
