analyzer: Weekly update and questions on extending c++ support.

2023-07-31 Thread Benjamin Priour via Gcc
Hi David, (subject's line totally stolen inspired from Eric's) Last week as you know had some special circumstances therefore not much has been done. I've changed my in-progress patch about trimming the system headers event to fit your suggestions from https://gcc.gnu.org/pipermail/gcc-patches/20

Re: Calling convention for Intel APX extension

2023-07-31 Thread Michael Matz via Gcc
Hello, On Sun, 30 Jul 2023, Thomas Koenig wrote: > > I've recently submitted a patch that adds some attributes that basically > > say "these-and-those regs aren't clobbered by this function" (I did them > > for not clobbered xmm8-15). Something similar could be used for the new > > GPRs as well.

[Predicated Ins vs Branches] O3 and PGO result in 2x performance drop relative to O2

2023-07-31 Thread Changbin Du via Gcc
Hello, folks. This is to discuss Gcc's heuristic strategy about Predicated Instructions and Branches. And probably something needs to be improved. [The story] Weeks ago, I built a huffman encoding program with O2, O3, and PGO respectively. This program is nothing special, just a random code I foun

Re: [Predicated Ins vs Branches] O3 and PGO result in 2x performance drop relative to O2

2023-07-31 Thread Richard Biener via Gcc
On Mon, Jul 31, 2023 at 2:57 PM Changbin Du via Gcc wrote: > > Hello, folks. > This is to discuss Gcc's heuristic strategy about Predicated Instructions and > Branches. And probably something needs to be improved. > > [The story] > Weeks ago, I built a huffman encoding program with O2, O3, and PGO

Re: analyzer: Weekly update and questions on extending c++ support.

2023-07-31 Thread David Malcolm via Gcc
On Mon, 2023-07-31 at 14:19 +0200, Benjamin Priour wrote: > Hi David, Hi Benjamin > > (subject's line totally stolen inspired from Eric's) :) > Last week as you know had some special circumstances therefore not > much has > been done. FWIW you still seem to have got a lot done. > > I've cha

Add clang's invalid-noreturn warning flag

2023-07-31 Thread Julian Waters via Gcc
Please review a patch to add clang's invalid-noreturn flag to toggle noreturn warnings. This patch keeps the old behaviour of always warning on every noreturn violation, but unlike clang also adds an extra layer of fine tuning by turning invalid-noreturn into a warning with levels, where level 1 w

Re: Add clang's invalid-noreturn warning flag

2023-07-31 Thread Andrew Pinski via Gcc
On Mon, Jul 31, 2023 at 8:18 PM Julian Waters via Gcc wrote: > > Please review a patch to add clang's invalid-noreturn flag to toggle > noreturn warnings. This patch keeps the old behaviour of always warning on > every noreturn violation, but unlike clang also adds an extra layer of fine > tuning