On 3/30/20 7:54 PM, Joseph Myers wrote:
Email sending for user branches makes perfect sense, to make visible the
development going on.
If so, can we then come up with a naming convention that will block the email
sending. I mean something like me/PR123456-fix-that-private?
I see the limitation
On 26/03/2020 22:30, David Malcolm via Gcc wrote:
I wrote a blog post "Static analysis in GCC 10" giving an idea of the
current status of the -fanalyzer feature:
https://developers.redhat.com/blog/2020/03/26/static-analysis-in-gcc-10/
At some point I'll write up the material for our changes.html
Hi there! I would like to choose a project called “Parallelize compilation
using threads, part two”. My first programming language was C++ at school.
I used it for competitive programming. Later in university I have improved
this skill by taking courses related to C/C++. Precisely, Programming 1
co
Hi Jozef,
On Thu, Mar 26, 2020 at 12:33:38PM +, Jozef Lawrynowicz wrote:
> In some cases, I can fix the CFA offset by marking these epilogue insns as
> frame_related anyway, and adding reg notes which describe the stack pointer
> operations. For some other epilogue insns, marking them frame_re
On 3/26/20 4:27 PM, Bernd Edlinger wrote:
> On 3/26/20 4:16 PM, Christopher Faylor wrote:
>> On Wed, Mar 25, 2020 at 09:29:03PM +0100, Bernd Edlinger wrote:
>>> -On 3/25/20 7:55 PM, Christopher Faylor wrote:
On Wed, Mar 25, 2020 at 04:23:02PM +0700, Arseny Solokha wrote:
> I believe the ca
