search for: r266414

...; Since I haven't heard any objections to the direction, I'm planning to > commit this (step 4) when I find some cycles; likely over the weekend. > > To make this more concrete (in case someone is silently concerned) I've > posted my WIP patches below. They apply cleanly to r266414. There are > a few mechanical changes missing that are tracked in the commit > messages (such as LangRef, or new tests in some cases). To get > `ninja check` to pass after the final commit you'll need to run the > attached upgrade script. The clang changes are truly uninteresting...

I have no objections to any of this FWIW :) -eric On Tue, Mar 29, 2016 at 6:46 PM Duncan P. N. Exon Smith < dexonsmith at apple.com> wrote: > > > On 2016-Mar-22, at 20:11, Eric Christopher <echristo at gmail.com> wrote: > > > >> On Tue, Mar 22, 2016 at 8:04 PM David Blaikie <dblaikie at gmail.com> > wrote: > >> +pcc, who had some other

...t heard any objections to the direction, I'm planning to > > commit this (step 4) when I find some cycles; likely over the weekend. > > > > To make this more concrete (in case someone is silently concerned) I've > > posted my WIP patches below. They apply cleanly to r266414. There are > > a few mechanical changes missing that are tracked in the commit > > messages (such as LangRef, or new tests in some cases). To get > > `ninja check` to pass after the final commit you'll need to run the > > attached upgrade script. The clang changes are...

...I'm planning to > >> > commit this (step 4) when I find some cycles; likely over the weekend. > >> > > >> > To make this more concrete (in case someone is silently concerned) > I've > >> > posted my WIP patches below. They apply cleanly to r266414. There > are > >> > a few mechanical changes missing that are tracked in the commit > >> > messages (such as LangRef, or new tests in some cases). To get > >> > `ninja check` to pass after the final commit you'll need to run the > >> > attach...

> On 2016-Mar-22, at 20:11, Eric Christopher <echristo at gmail.com> wrote: > >> On Tue, Mar 22, 2016 at 8:04 PM David Blaikie <dblaikie at gmail.com> wrote: >> +pcc, who had some other ideas/patch out for improving memory usage of debug info >> +Reid, who's responsible for the windows/CodeView/PDB debug info which is motivating some of the ideas about

...nning to >> >> > commit this (step 4) when I find some cycles; likely over the weekend. >> >> > >> >> > To make this more concrete (in case someone is silently concerned) I've >> >> > posted my WIP patches below. They apply cleanly to r266414. There are >> >> > a few mechanical changes missing that are tracked in the commit >> >> > messages (such as LangRef, or new tests in some cases). To get >> >> > `ninja check` to pass after the final commit you'll need to run the >> >>...