[cfe-dev] API/ABI changes analysis reports for libc++

[Eric Fiselier via cfe-dev]

Hi Andrey,

Thanks for the links! They look amazing. I'll have to look into the tools
used to generate them.

> The report on API/ABI changes in the latest releases of libc++

Pedantically this just seems to report ABI changes, not non-ABI breaking
API changes.

Do you have results for ToT libc++ (which contains a bunch of ABI changes)?
Detecting ABI breaking changes in libc++ is very important, and ideally
should be done per-commit.
Currently we have very primitive ABI checking using the export list
provided by `nm` or `objdump`, but I'm interested
in using these tools as well.

/Eric

On Fri, Dec 2, 2016 at 5:54 AM, Renato Golin via cfe-dev <
cfe-dev at lists.llvm.org> wrote:

> On 2 December 2016 at 12:13, Ponomarenko Andrey via cfe-dev
> <cfe-dev at lists.llvm.org> wrote:
> > Hello,
> >
> > The report on API/ABI changes in the latest releases of libc++:
> https://abi-laboratory.pro/tracker/timeline/libcxx/
> >
> > The same for libc++abi: https://abi-laboratory.pro/
> tracker/timeline/libcxxabi/
>
> Hi Andrey,
>
> This is really interesting, thanks!
>
> I wonder why is the tool picking on comment changes on headers:
>
> https://abi-laboratory.pro/tracker/headers_diff/glib/2.
> 51.0/current/diff.html
>
> cheers,
> --renato
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20161202/cde3f667/attachment.html>