<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Stefan,<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Dec 3, 2018, at 06:10, Stefan Kanthak via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">"Tim Northover" <<a href="mailto:t.p.northover@gmail.com" class="">t.p.northover@gmail.com</a>> wrote:<br class=""><br class=""><blockquote type="cite" class="">Hi,<br class=""><br class="">On Sat, 1 Dec 2018 at 17:37, Stefan Kanthak via llvm-dev<br class=""><<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:<br class=""><blockquote type="cite" class="">Compile the following functions with "-O3 -target amd64"<br class=""></blockquote><br class="">You've been advised before, but you really need to start reporting<br class="">these as bugs[*] if you actually care about them.<br class=""></blockquote><br class="">These ain't my bugs, these are LLVM's bugs.<br class=""></div></div></blockquote><div><br class=""></div><div>FWIW, I think you're misunderstanding Tim's intent there. He's not saying they're your bugs, he's just saying they need to be reported in the correct place.</div><br class=""><blockquote type="cite" class=""><div class=""><div class="">I don't use LLVM, I just dared to write some posts which pinpoint<br class="">deficiencies and bugs in it. You should see this as COURTESY.<br class="">The least I expect from any software developer, and especially a<br class="">"foundation", is to take action on bug reports, INDEPENDENT how they<br class="">are reported.<br class=""><br class=""><blockquote type="cite" class="">llvm-dev is<br class="">basically a black-hole as far as bugs go: if no-one takes enough of an<br class="">interest to either fix or file a bug within a day or two, the issue<br class="">will be completely forgotten. The list is intended for discussion of<br class="">issues and future designs, not reporting them.<br class=""></blockquote><br class="">That's clearly LLVM's problem.<br class=""><br class=""><blockquote type="cite" class="">It seems you got lucky and someone did file at least one report from<br class="">one of these threads;<br class=""></blockquote><br class="">You got that backwards: YOU are lucky that I took the time to report<br class="">these bugs!<br class=""><br class=""><blockquote type="cite" class="">you should expect that to become less frequent.<br class="">People are willing to assume the best of new contributors, but by the<br class="">time you reach a dozen threads without actually engaging with the<br class="">community's procedures that goodwill starts to look a bit threadbare.<br class=""><br class="">Cheers.<br class=""><br class="">Tim.<br class=""><br class="">[*] <a href="https://llvm.org/docs/Contributing.html" class="">https://llvm.org/docs/Contributing.html</a><br class=""></blockquote><br class="">| If you are working with LLVM and run into a bug, we definitely want<br class="">| to know about it.<br class=""></div></div></blockquote><div><br class=""></div><span style="background-color: rgba(255, 255, 255, 0);" class="">The sentence following that one provides instructions on how to report bugs:</span></div><div><div><span style="background-color: rgba(255, 255, 255, 0);" class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>Please let us know and follow the instructions in <a class="internal reference" href="https://llvm.org/docs/HowToSubmitABug.html" style="color: rgb(202, 121, 0);"><span class="doc">How to submit an LLVM bug report</span></a> to create a bug report.</span></div><div class=""><span style="background-color: rgba(255, 255, 255, 0);" class=""><br class=""></span></div><div class=""><span style="background-color: rgba(255, 255, 255, 0);" class="">Those instructions say:</span></div><div class=""><span style="background-color: rgba(255, 255, 255, 0);" class=""><span class="Apple-tab-span" style="white-space:pre"> </span>Once you have a reduced test-case, go to <a class="external reference" href="https://bugs.llvm.org/enter_bug.cgi" style="color: rgb(202, 121, 0);">the LLVM Bug Tracking System</a> and fill out the form with the necessary details (note that you don’t need to pick a category, just use the “new-bugs” category if you’re not sure).</span></div><div class=""><span style="background-color: rgba(255, 255, 255, 0);" class="">You already seem to have reduced test cases (Thanks) so they just need to be reported to the bug tracker.</span></div><div class=""><br class=""></div><div class="">Unfortunately, it's a bit harder to create an account with the bug tracker than it ought to be as there's been trouble with spam. <a href="mailto:bugs-admin@lists.llvm.org" class="">bugs-admin@lists.llvm.org</a> can set you up with an account.</div></div><div><br class=""></div><div><blockquote type="cite" class=""><div class=""><div class="">I DONT WORK WITH LLVM.<br class="">I was just curious whether it shows bugs and deficiencies I saw in<br class="">two other C compilers, and documented them.<br class="">You and your users suffer from these bugs and deficiencies, not me.<br class=""><br class="">regards<br class="">Stefan<br class="">_______________________________________________<br class="">LLVM Developers mailing list<br class=""><a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a><br class="">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev<br class=""></div></div></blockquote></div><br class=""></body></html>