<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 2, 2016, at 7:05 AM, Gábor Horváth <<a href="mailto:xazax.hun@gmail.com" class="">xazax.hun@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><br class="Apple-interchange-newline"><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><div class="gmail_quote" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">On 12 February 2016 at 01:16, Hans Wennborg via cfe-dev<span class="Apple-converted-space"> </span><span dir="ltr" class=""><<a href="mailto:cfe-dev@lists.llvm.org" target="_blank" class="">cfe-dev@lists.llvm.org</a>></span><span class="Apple-converted-space"> </span>wrote:<br class=""><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;">Dear lots of people,<br class=""><br class="">The first comments on the 3.7 release expressed surprise that there<br class="">were no changes to the X86 or ARM targets. There had of course been a<br class="">lot of hard work and many changes, but none of it was mentioned in the<br class="">release notes.<br class=""><br class="">Please help make the release notes more comprehensive this time. The<br class="">notes are of course not as important as the actual code, but they do<br class="">get read, and they are a good way of telling users about all the hard<br class="">work you have done in the past six months.<br class=""><br class="">If you made any changes in the 3.8 time span that might be worth<br class="">mentioning, please add them to the release notes --- it does not have<br class="">to be big-ticket items. If you saw someone else commit something<br class="">interesting, prod them to write a note about it.<br class=""><br class="">The 3.8-rc2 notes can be seen at [1]. To add something, commit it<br class="">directly to the branch, or if you prefer, send me a patch or even just<br class="">an email with some text. I would be very happy if we can get these<br class="">into good shape by the beginning of next week.<br class=""><br class=""><br class="">Some things that might be worth mentioning, in no particular order:<br class="">(based partially on Alex Bradbury's LLVM Weekly; thanks!)<br class=""><br class="">- Intel, ARM, PowerPC, MIPS, SPARC, Hexagon, ..., target maintainers,<br class="">please write something about your target.<br class=""><br class="">- Eric: should the new C API Changes part of the developer policy be<br class="">pointed out? Maybe in relation to where we mention changes to the C<br class="">API?<br class=""><br class="">- David: can you write something about the new IR for exception<br class="">handling? Maybe just point into the ExceptionHandling doc?<br class=""><br class="">- Alex L: I've seen a lot of MIR patches but don't know the status.<br class="">Anything to mention in the release notes?<br class=""><br class="">- Dylan: should we mention the new AVR target, or is it too early?<br class=""><br class="">- Richard: anything on the C++ front? What's the status on coroutines?<br class=""><br class="">- Jonathan and other OpenMP folks: it's no longer behind a flag; would<br class="">be great to get some notes on this.<br class=""><br class="">- Artem: there's been a bunch of CUDA patches. Anything that should be<br class="">mentioned in the release notes?<br class=""><br class="">- Jordan & Anna: any new checkers that should be mentioned?<br class=""></blockquote><div class=""><br class=""></div><div class="">I did not see any response yet, so I cherry picked some changes:<br class=""><br class=""></div><div class="">- There are better diagnostics for loading analyzer plugins, when the static analyzer is invoked from libtooling.<br class=""></div><div class="">- New checks introduced for iOS / OS X localizability issues.<br class=""></div><div class="">- New warning, when a nested if has the same condition (without side effects) as the outer if.<br class=""></div><div class="">- New checks for the ObjC lightweight generics feature.<br class=""></div><div class="">- New checks that utilize nullability qualifiers.<br class=""></div><div class="">- New check to find unsafe uses of vforked projects.<br class=""></div><div class="">- New check to detect excess padding in records.<br class=""></div><div class="">- Better modelling memcpy.<br class=""></div><div class="">- Better modelling messaging to nil in ObjC.<br class=""></div><div class="">- New API to generate error nodes.<br class=""></div><div class="">- Fixes to the modelling of pointer arithmetic.<br class=""></div><div class="">- Better handle range switch cases.<br class=""></div><div class="">- Better handle realloc, fix some false positives in malloc-overflow check.<br class=""></div><div class="">- Better model const methods.<br class=""></div><div class="">- Support for lambda functions.<br class=""></div><div class="">- Experimental feature to widen loops. When enabled, the analyzer will have greater coverage in code that has loops with high constant bounds.<br class=""></div><div class="">- Generate bug hash as an identifier for each report. It can be used to track bugs in evolving code.<br class=""></div><div class="">- Improve the modelling of static initializers.<br class=""></div><div class="">- Better model stack allocated blocks in Obj-C.<br class=""></div><div class="">- Better model nullptr_t.<br class=""></div><div class="">- Better model casts between integral types.<br class=""></div><div class="">- Various other improvements in the analyzer engine.<br class=""><br class=""></div><div class="">Feel free to reword and pick some of those into the release notes.<br class=""></div><div class=""> </div></div></div></blockquote><div><br class=""></div>Thank you Gabor,</div><div><br class=""></div><div>We’ve updated the Static Analyzer notes with the following summary. Looks like there are no glaring omissions from the list you’ve provided. I chose not to list the specific improvements in the core to keep this focused and user-friendly.</div><div><br class=""></div><div><div>+The scan-build and scan-view tools will now be installed with clang. Use these</div><div>+tools to run the static analyzer on projects and view the produced results.</div><div>+</div><div>+Static analysis of C++ lambdas has been greatly improved, including</div><div>+interprocedural analysis of lambda applications.</div><div>+</div><div>+Several new checks were added:</div><div>+</div><div>+- The analyzer now checks for misuse of ``vfork()``.</div><div>+- The analyzer can now detect excessively-padded structs. This check can be</div><div>+ enabled by passing the following command to scan-build:</div><div>+ ``-enable-checker optin.performance.Padding``.</div><div>+- The checks to detect misuse of ``_Nonnull`` type qualifiers as well as checks</div><div>+ to detect misuse of Objective-C generics were added.</div><div>+- The analyzer now has opt in checks to detect localization errors in Coca</div><div>+ applications. The checks warn about uses of non-localized ``NSStrings``</div><div>+ passed to UI methods expecting localized strings and on ``NSLocalizedString``</div><div>+ macros that are missing the comment argument. These can be enabled by passing</div><div>+ the following command to scan-build:</div><div>+ ``-enable-checker optin.osx.cocoa.localizability``.</div><div> </div></div><div><br class=""><blockquote type="cite" class=""><div class=""><div class="gmail_quote" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;"><br class="">- Chih-Hung: should the notes mention the emutls-style TLS model?<br class=""><br class="">- Lang: you did a lot of work on the Kalidoscope tutorial. Maybe we<br class="">should mention that?<br class=""><br class="">.. tell me what I missed :-)<br class=""><br class="">Thanks,<br class="">Hans<br class=""><br class=""> [1].<span class="Apple-converted-space"> </span><a href="http://llvm.org/pre-releases/3.8.0/#rc2" rel="noreferrer" target="_blank" class="">http://llvm.org/pre-releases/3.8.0/#rc2</a>.<br class="">_______________________________________________<br class="">cfe-dev mailing list<br class=""><a href="mailto:cfe-dev@lists.llvm.org" class="">cfe-dev@lists.llvm.org</a><br class=""><a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank" class="">http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a></blockquote></div></div></blockquote></div><br class=""></body></html>