On Wed, Nov 27, 2019 at 06:05:37PM +0000, Ramsay Jones wrote: > On 27/11/2019 17:48, Luc Van Oostenryck wrote: > > On Wed, Nov 27, 2019 at 05:15:20PM +0000, Ramsay Jones wrote: > >> > >> I was going to just test 'luc/int128_ctype', but looking at the output > >> of 'git log --oneline --graph master..luc/int128_ctype' I can see that > >> several other branches are merged into the result. So, I will apply > >> the patches from the mailing list directly to test them (hmm, _hopefully_ > >> tonight). > > > > Hi Ramsay, > > > > Sorry, I should have added in the cover letter that the series > > with all related patches is available at: > > git://github.com/lucvoo/sparse-dev.git next > > Hmm, but that _also_ contains several other branches not contained > in 'master', thus: > > $ git --no-pager log --oneline --graph master..luc/next > * 4a8aa8d1 (luc/tip, luc/next) cgcc: add support for riscv64 > * df14d253 arch: fix wchar_t & wint_t for openbsd > * 662ed740 arch: add missing predefines for PPC > * 1ff97d3a arch: add missing predfines: __amd64 & __amd64__ > * d8754f2c cgcc: filter-out -msize-long & -msize-llp64 > * 7efa090f (luc/int128_ctype) spec: replace lllong_ctype by int128_ctype Yes, indeed. It's how these patches have been written and tested, though. They're supposed to be the cherries on top of the cake. But I think that only 'df14d253 arch: fix wchar_t & wint_t for openbsd' may have some dependencies on one of these branches. For the 3 others it shouldn't matter. Best regards, -- Luc
