search for: abi_tag

...feel responsible for a particular target, e.g. X86, ARM, MIPS, etc., please help give those release notes some love. Here are some examples we might want to mention (thanks LLVM Weekly!). If you're cc'd on this email, you're mentioned below. - Dmitry, Renato: the Clang notes mention abi_tag. Do we want to expand the text here a little? Link to the PR? - Teresa, Mehdi: there's a "Introduction of ThinLTO [..] ping Mehdi/Teresa before the release if not done" note, so here's the ping :-) We should link to the blog post as well. - Chris Bieneman, there's a "no...

On 3 August 2016 at 10:46, Renato Golin <renato.golin at linaro.org> wrote: > We certainly do. This is a big deal. I'll write up something and let > Dmitry correct my mistakes. :) Done. > We'll also add the ARM/AArch64 changelogs. Done. :) cheers, --renato

...'m going to do it to a wider audience: Shall we sync our upstream release with the bulk of other downstream ones as well as OS distributions? This work involves a *lot* of premises that are not encoded yet, so we'll need a lot of work from all of us. But from the recent problems with GCC abi_tag and the arduous job of downstream release managers to know which patches to pick, I think there has been a lot of wasted effort by everyone, and that generates stress, conflicts, etc. I'd also like to reinforce the basic idea of software engineering: to use the same pattern for the same proble...

...ync our upstream release with the bulk of other downstream >> ones as well as OS distributions? >> >> >> This work involves a *lot* of premises that are not encoded yet, so >> we'll need a lot of work from all of us. But from the recent problems >> with GCC abi_tag and the arduous job of downstream release managers to >> know which patches to pick, I think there has been a lot of wasted >> effort by everyone, and that generates stress, conflicts, etc. >> >> I'd also like to reinforce the basic idea of software engineering: to >...