<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Aug 21, 2009, at 2:23 PM, Bill Wendling wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On Aug 19, 2009, at 4:30 PM, Tanya Lattner wrote:<br><br><blockquote type="cite">On Aug 4, 2009, at 5:33 AM, Anton Korobeynikov wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">Hello, Martin<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">llvm-gcc-4.2-2.5 is failing to build from source on arm, sparc,<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">powerpc and ia64, only succeeding on i386 and amd64:<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><a href="http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=llvm-gcc-4.2;dist=unstable">http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=llvm-gcc-4.2;dist=unstable</a><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">so it looks like the 2.5 release was never properly tested before it<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">was published.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Unfortunately, ia64 and sparc were never considered as a 'tier-1'<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">targets for llvm-gcc, there was noone who cared about it. Also, our<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">linux resources are pretty limited, thus both ppc and arm were broken<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">at the time for 2.5 release.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Hopefully things will be much better with the coming 2.6 release, at<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">least one might expect arm and ppc to be more or less ok. ia64 support<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">was completely dropped and sparc should be brokens as of time of 2.5.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I just want to comment on this. We test our releases very throughly for supported targets. Supported means that they are actively maintained and tested day after day. If no one steps up to be a maintainer for these targets, then they will not become a part of the release criteria.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">With that said, we only qualified for x86-32, x86-64, mingw32, and ppc (mac os 10.5 only). So pretty much all the ones that are failing were not supported for 2.5. This list is only slightly expanded for 2.6, and will not include arm, ia64, sparc, or ppc.<br></blockquote><br>For what it's worth, Daniel and I recently set up a Mac OS 10.5 PPC G5 box as a build bot machine. I've been monitoring it, so it's doing well for the 2.6 release. :-)<br><br></div></blockquote><div><br></div><div>Now you set yourself up. Would you be willing to qualify 2.6 for Mac OS 10.5 ppc? If you have time,that would be very useful. :) If not, I understand.</div><div><br></div><div>-Tanya</div><br><blockquote type="cite"><div>-bw<br><br><blockquote type="cite">arm will probably work with 2.5, but unless someone wants to qualify it for the release (I do not have a volunteer), then it will not be on the list of supported targets.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">We'd love help with these targets. Ideally, we need someone to set up an appropriate buildbot and actively monitor it and fix issues or file bug reports for things that come up.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Thanks,<br></blockquote><blockquote type="cite">Tanya<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">If the issues and fixes are "known", can you make them known to the<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">public, for example by producing a 2.5.1 with the worst bugs fixed, or<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">by documenting the issues and patches in the "Known problems" section?<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">It would be a big help to all the distro maintainers.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">You might want to stick with next 2.6 release, which is scheduled to<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">be out within next 1.5 months<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I would like to comment on some other bugs as well:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">478535: there are no plans to support of legacy IBM S390 platform,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">only 64 bit one (that's s390x in tartget triple). The current plans<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">are to use clang only, not llvm-gcc, however I might be able to find<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">few hours to give llvm-gcc a try.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">539496: There are no plans to support ARMv4 in LLVM. As for ToT ARM<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">builds of llvm-gcc (both for bare-metal arm-elf and normal<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">arm-none-linux-gnueabi triples) is broken due to two PRs: 4680, 4681<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">511721: I believe it should be fixed on ToT.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">518592: Sounds like compiler / linker problem, it's not LLVM related at all<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">-- <br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">With best regards, Anton Korobeynikov<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Faculty of Mathematics and Mechanics, Saint Petersburg State University<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">_______________________________________________<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">LLVM Developers mailing list<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="mailto:LLVMdev@cs.uiuc.edu">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">LLVM Developers mailing list<br></blockquote><blockquote type="cite"><a href="mailto:LLVMdev@cs.uiuc.edu">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a><br></blockquote><blockquote type="cite"><a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br></blockquote><br></div></blockquote></div><br></body></html>