[Bug bootstrap/88668] Code generated was different for PowerPC when build!=host compared to build=host

2019-01-03 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88668 --- Comment #6 from Andrew Pinski --- So the correct fix is to add --enable-targets=$enable_targets to ${realsrcdir}/configure command instead.

[Bug bootstrap/88668] Code generated was different for PowerPC when build!=host compared to build=host

2019-01-03 Thread umesh.kalappa0 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88668 --- Comment #5 from Umesh Kalappa --- Andrew unfortunately your suggestion didn't worked for us and there was mis-lead in our fix and the actual change was like --- a/gcc/configure +++ b/gcc/configure @@ -11795,15 +11795,16 @@ else

[Bug bootstrap/88668] Code generated was different for PowerPC when build!=host compared to build=host

2019-01-03 Thread umesh.kalappa0 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88668 --- Comment #4 from Umesh Kalappa --- Thank you Andrew for the suggestions and let us try the same and update here .

[Bug bootstrap/88668] Code generated was different for PowerPC when build!=host compared to build=host

2019-01-02 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88668 --- Comment #3 from Andrew Pinski --- (In reply to Andrew Pinski from comment #2) > > On windows with configure like > > --host i686-w64-mingw32 > > But build is then guessed using config.guess. > Then you have a build!=host case. I should say

[Bug bootstrap/88668] Code generated was different for PowerPC when build!=host compared to build=host

2019-01-02 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88668 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|