Re: x86_64 build error converting poly_value_estimate_kind

2020-12-17 Thread Martin Sebor via Gcc-patches
On 12/17/20 12:12 PM, H.J. Lu wrote: On Thu, Dec 17, 2020 at 11:07 AM Martin Sebor via Gcc-patches wrote: The top of trunk fails to build with the error below. I haven't spent any time debugging it except to look at git log where the description for r11-6238 mentions the function also referen

[PATCH] libstdc++: Skip atomic instructions in _Sp_counted_base::_M_release when both counts are 1

2020-12-17 Thread Maged Michael via Gcc-patches
Please find a proposed patch for _Sp_counted_base::_M_release to skip the two atomic instructions that decrement each of the use count and the weak count when both are 1. I proposed the general idea in an earlier thread ( https://gcc.gnu.org/pipermail/libstdc++/2020-December/051642.html) and got us

RE: [PATCH][GCC] arm: Add support for Cortex-A78C

2020-12-17 Thread Przemyslaw Wirkus via Gcc-patches
> > Subject: [PATCH][GCC] arm: Add support for Cortex-A78C > > > > This patch adds support for -mcpu=cortex-a78c command line option. > > For more information about this processor, see [0]: > > > > [0] https://developer.arm.com/ip-products/processors/cortex-a/cortex- > > a78c > > > > OK from master

Re: [PATCH] c++: Diagnose unstable satisfaction results

2020-12-17 Thread Jason Merrill via Gcc-patches
On 12/17/20 12:24 PM, Patrick Palka wrote: On Thu, 17 Dec 2020, Patrick Palka wrote: On Fri, Dec 11, 2020 at 4:55 PM Patrick Palka wrote: On Fri, 11 Dec 2020, Jason Merrill wrote: On 12/11/20 10:31 AM, Patrick Palka wrote: On Thu, 10 Dec 2020, Patrick Palka wrote: On Thu, 10 Dec 2020, J

Re: C++ 20 modules

2020-12-17 Thread Nathan Sidwell
As yesterday, several issues fixed: * 98315 Rainer confirmed fixed * 98300 Reported noted progress, first patch committed * An m68k 'nop' issue fixed * 98340 Another clang issue, fixed * 98324 One PIC issue fixed. * 98316 solaris libs, Rainer posted patch, which LGTM * 98324 bootstrap with lto/PI

[PATCH] c++: fix string literal member initializer bug [PR90926]

2020-12-17 Thread Thomas Greenslade (thomgree) via Gcc-patches
build_aggr_conv did not correctly handle string literal member initializers. Extended can_convert_array to handle this case. The additional checks of compatibility of character types, and whether string literal will fit, would be quite complicated, so are deferred until the actual conversion takes

Re: [PATCH] Update default_estimated_poly_value prototype in targhooks.h

2020-12-17 Thread Kyrylo Tkachov via Gcc-patches
Thanks HJ. Sorry for missing this in my testing. Kyrill From: H.J. Lu Sent: 17 December 2020 19:06 To: Richard Sandiford ; Kyrylo Tkachov via Gcc-patches ; Kyrylo Tkachov Subject: [PATCH] Update default_estimated_poly_value prototype in targhooks.h On Thu, Dec

[PATCH] libstdc++: Add support for C++20 barriers

2020-12-17 Thread Thomas Rodgers
From: Thomas Rodgers Cleans up a few things mentioned on IRC. Adds libstdc++/ChangeLog: * doc/doxygen/user.cfg.in: Add new header. * include/Makefile.am (std_headers): likewise. * include/Makefile.in: Regenerate. * include/precompiled/stdc++.h: Add new header.

[PATCH v6] Practical improvement to libgcc complex divide

2020-12-17 Thread Patrick McGehearty via Gcc-patches
Changes in this version from Version 5: Commit message change: Information for Changelogs put in proper format. Thanks go to Jakub Jelinek for enlightening me how to do that and providing an excellent example. c-cppbuiltin.c - Fixed various formatting issues regard

Re: [PATCH 3/4] libstdc++: Add floating-point std::to_chars implementation

2020-12-17 Thread Patrick Palka via Gcc-patches
On Thu, Dec 17, 2020 at 9:32 AM Jonathan Wakely wrote: > > On 19/08/20 17:57 -0400, Patrick Palka via Libstdc++ wrote: > >On Wed, 22 Jul 2020, Patrick Palka wrote: > > > >> On Mon, 20 Jul 2020, Patrick Palka wrote: > >> > >> > On Mon, 20 Jul 2020, Jonathan Wakely wrote: > >> > > >> > > On 20/07/20

Go testsuite patch committed: Handle +builds line correctly in testsuite

2020-12-17 Thread Ian Lance Taylor via Gcc-patches
This patch to the Go testsuite driver changes it to handle +build lines correctly, which is to say, in the same way that they are handled by the upstream test driver. Update several tests from the upstream repo to use "gc" and "!gccgo" as appropriate so that tests continue to pass. This cleans up

<    1   2