[Bug ada/56909] New: [4.8 regression] Ada: s-atopri.adb:multiple undefined references on mingw32

2013-04-10 Thread mail2arthur at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56909 Bug #: 56909 Summary: [4.8 regression] Ada: s-atopri.adb:multiple undefined references on mingw32 Classification: Unclassified Product: gcc Version: unknown

[Bug ada/56909] [4.8 regression] Ada: s-atopri.adb:multiple undefined references on mingw32

2013-04-10 Thread mail2arthur at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56909 --- Comment #1 from Arthur Zhang 2013-04-10 16:32:49 UTC --- Less undefined references if add '--with-arch=i486 --with-tune=i686' to configure. s-atopri.o: In function `system__atomic_primitives__lock_free_read_64': e:\test1\bd\wk\build

[Bug ada/56909] [4.8 regression] s-atopri.adb:multiple undefined references on mingw32 --with-arch=i486

2013-04-11 Thread mail2arthur at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56909 --- Comment #3 from Arthur Zhang 2013-04-11 22:08:54 UTC --- The only configure option works for now is '--with-arch=i686'. Thanks.

[Bug ada/56909] [4.8 regression] s-atopri.adb:multiple undefined references on mingw32 --with-arch=i486

2013-04-12 Thread mail2arthur at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56909 --- Comment #5 from Arthur Zhang 2013-04-12 20:39:42 UTC --- (In reply to comment #4) > > The only configure option works for now is '--with-arch=i686'. Thanks. > > You're welcome. But you should remove it, it probably slows down the >

[Bug ada/56909] [4.8 regression] s-atopri.adb:multiple undefined references on mingw32 --with-arch=i486

2013-04-13 Thread mail2arthur at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56909 --- Comment #7 from Arthur Zhang 2013-04-14 04:12:35 UTC --- clarification: On MinGW, GCC 4.7.x Ada built successfully with default (no -with-arch or -with-tune) configure. GCC 4.8.0 s-atopri.* changes breaks same configure: 1. wit

[Bug ada/56909] [4.8 regression] s-atopri.adb:multiple undefined references on mingw32

2013-04-14 Thread mail2arthur at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56909 --- Comment #10 from Arthur Zhang 2013-04-14 22:09:34 UTC --- (In reply to comment #9) > > On MinGW, GCC 4.7.x Ada built successfully with default (no -with-arch or > > -with-tune) configure. > > > > GCC 4.8.0 s-atopri.* changes breaks

[Bug ada/56909] [4.8 regression] s-atopri.adb:multiple undefined references on mingw32

2013-04-14 Thread mail2arthur at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56909 --- Comment #11 from Arthur Zhang 2013-04-14 23:12:48 UTC --- Will '--exec-prefix=mingw32' work?

[Bug ada/56909] [4.8 regression] s-atopri.adb:multiple undefined references on mingw32

2013-04-17 Thread mail2arthur at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56909 Arthur Zhang changed: What|Removed |Added Status|RESOLVED|NEW Resolution|WONTFIX

[Bug ada/56909] [4.8 regression] s-atopri.adb:multiple undefined references on mingw32

2013-04-17 Thread mail2arthur at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56909 --- Comment #14 from Arthur Zhang 2013-04-17 21:02:14 UTC --- (In reply to comment #13) > > What is the benefit to use '--build=i686-pc-mingw32' than > > '--with-arch=i686'? > > It doesn't force -march=i686 by default. Why below outp

[Bug ada/56909] [4.8 regression] s-atopri.adb:multiple undefined references on mingw32

2013-04-18 Thread mail2arthur at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56909 --- Comment #16 from Arthur Zhang 2013-04-18 14:48:50 UTC --- (In reply to comment #15) > > Why below output has '-march=pentiumpro'? > > I think it's the autodetected arch, but maybe I'm confused. Never mind. If you mean autodetecte

[Bug ada/56909] [4.8 regression] s-atopri.adb:multiple undefined references on mingw32

2013-04-23 Thread mail2arthur at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56909 --- Comment #18 from Arthur Zhang 2013-04-23 14:31:12 UTC --- (In reply to comment #17) > What is the driving factor that is causing you to want to make the gcc build > so > complicated? I am building release packages for MinGW proje