git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: js/gcc-8-and-9, was Re: What's cooking in git.git (Jun 2019, #04; Fri, 14)

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jun 18, 2019, 10:26 UTC
Message-ID
<nycvar.QRO.7.76.6.1906181221360.44@tvgsbejvaqbjf.bet>
In-Reply-To
<xmqqpnncrnr0.fsf@gitster-ct.c.googlers.com>
Hi Junio,
On Mon, 17 Jun 2019, Junio C Hamano wrote:
Show 24 quoted lines
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > On Fri, 14 Jun 2019, Junio C Hamano wrote:
> >
> >> * js/gcc-8-and-9 (2019-06-13) 4 commits
> >>  - config: avoid calling `labs()` on too-large data type
> >>  - winansi: simplify loading the GetCurrentConsoleFontEx() function
> >>  - kwset: allow building with GCC 8
> >>  - poll (mingw): allow compiling with GCC 8 and DEVELOPER=1
> >>
> >>  Code clean-up for new compilers.
> >>
> >>  The 'kwset' one may want to be discussed a bit longer.  Perhaps
> >>  merge the other three earlier to 'next' and then to 'master'
> >>  separately?
> >
> > Or just take the kwset one with an adjusted commit message because it may
> > turn out that the kwset update will be blocked for a while because of
> > licensing issues?
>
> Sorry, but I do not understand why you'd want to "take" one that you
> suspect may be blocked for a while.  I'd rather see us unblock the
> other ones that are unproblematic, without taking them hostage,
> which was what I meant.
My apologies for causing confusion.

What I *tried* to suggest is to take my minimal `kwset: allow building with GCC 8` together with the other three, as it fixes the build. Without it, the build is not fixed under `DEVELOPER=1`, it is still broken.

This would prevent me from upgrading GCC in Git for Windows' SDK to GCC v8 or v9, as that SDK is used to run all the CI builds.

Sure, having this small wrapper around `xmalloc()` would be a less elegant solution than the alternative (i.e. synchronize our `kwset` with upstream). But that alternative will take substantially longer to stabilize, and that would block the GCC upgrade substantially longer.

And I am quite confident that Gábor (or is it Szeder?) will be very able to rebase their changes on top of that small compile fix.

That's all I meant to say.

Ciao, Dscho

Previous: Junio C HamanoNext: Junio C Hamano
Message 4 of 14 in “What's cooking in git.git (Jun 2019, #04; Fri, 14)”
  1. Junio C HamanoJun 14, 2019
  2. js/gcc-8-and-9, was Re: What's cooking in git.git (Jun 2019, #04; Fri, 14)Johannes Schindelin, Jun 17, 2019
  3. Junio C HamanoJun 17, 2019
  4. Johannes SchindelinJun 18, 2019
  5. Junio C HamanoJun 19, 2019
  6. pw/rebase-abort-clean-rewritten, was Re: What's cooking in git.git (Jun 2019, #04; Fri, 14)Johannes Schindelin, Jun 17, 2019
  7. Phillip WoodJun 17, 2019
  8. Junio C HamanoJun 18, 2019
  9. Phillip WoodJun 20, 2019
  10. Johannes SchindelinJun 21, 2019
  11. sg/rebase-progress, was Re: What's cooking in git.git (Jun 2019, #04; Fri, 14)Johannes Schindelin, Jun 17, 2019
  12. ds/commit-graph-incremental (was Re: What's cooking in git.git (Jun 2019, #04; Fri, 14))Derrick Stolee, Jun 18, 2019
  13. Junio C HamanoJun 19, 2019
  14. Derrick StoleeJun 19, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.