Re: Re: [PATCH] [PHIOPT] Add A ? B + CST : B match and simplify optimizations

On Tue, Nov 8, 2022 at 4:51 PM 钟云德 wrote: > At 2022-11-08 22:58:34, "Richard Biener" > wrote: > > >On Sat, Nov 5, 2022 at 10:03 AM Zhongyunde via Gcc-patches > > wrote: > >> > >> > >> > -Original Message- > >> > From: Andrew Pinski [mailto:pins...@gcc.gnu.org] > >> > Sent: Saturday, Nove

RE: [PATCH 1/4]middle-end Support not decomposing specific divisions during vectorization.

On Tue, 8 Nov 2022, Tamar Christina wrote: > Ping. Jeff approved this already. I think it's OK if the rest of the series is approved. Richard. > > -Original Message- > > From: Tamar Christina > > Sent: Monday, October 31, 2022 11:35 AM > > To: Richard Biener > > Cc: gcc-patches@gcc.gn

Re: [PATCH 2/4] LoongArch: Add ftint{,rm,rp}.{w,l}.{s,d} instructions

On Wed, 2022-11-09 at 15:46 +0800, Lulu Cheng wrote: > There is a paragraph in the explanation information for the compile > parameter '-fno-fp-int-builtin-inexact' in the gcc.pdf document: > > "Do not allow the built-in functions ceil, floor, round and > trunc, > and their　float and long d

Re: [PATCH 1/4]middle-end Support not decomposing specific divisions during vectorization.

Ah sorry, i missed that one. Thanks, Tamar From: Richard Biener Sent: Wednesday, November 9, 2022 8:01 AM To: Tamar Christina Cc: gcc-patches@gcc.gnu.org ; nd ; jeffreya...@gmail.com Subject: RE: [PATCH 1/4]middle-end Support not decomposing specific divisions

RE: [PATCH 2/4]AArch64 Add implementation for pow2 bitmask division.

Ping > -Original Message- > From: Tamar Christina > Sent: Monday, October 31, 2022 11:35 AM > To: 'Tamar Christina' ; gcc-patches@gcc.gnu.org > Cc: nd ; Richard Earnshaw ; > Marcus Shawcroft ; Kyrylo Tkachov > ; Richard Sandiford > > Subject: RE: [PATCH 2/4]AArch64 Add implementation for

RE: [PATCH 3/4]AArch64 Add SVE2 implementation for pow2 bitmask division

ping > -Original Message- > From: Tamar Christina > Sent: Monday, October 31, 2022 11:35 AM > To: Tamar Christina ; gcc-patches@gcc.gnu.org > Cc: nd ; Richard Earnshaw ; > Marcus Shawcroft ; Kyrylo Tkachov > ; Richard Sandiford > > Subject: RE: [PATCH 3/4]AArch64 Add SVE2 implementation f

RE: [PATCH 4/4]AArch64 sve2: rewrite pack + NARROWB + NARROWB to NARROWB + NARROWT

ping > -Original Message- > From: Tamar Christina > Sent: Monday, October 31, 2022 11:35 AM > To: Tamar Christina ; gcc-patches@gcc.gnu.org > Cc: Richard Earnshaw ; nd ; > Richard Sandiford ; Marcus Shawcroft > > Subject: RE: [PATCH 4/4]AArch64 sve2: rewrite pack + NARROWB + > NARROWB to

Re: [RFC] propgation leap over memory copy for struct

On Wed, 9 Nov 2022, Jiufu Guo wrote: > Jiufu Guo via Gcc-patches writes: > > > Richard Biener writes: > > > >> On Tue, 1 Nov 2022, Jiufu Guo wrote: > >> > >>> Segher Boessenkool writes: > >>> > >>> > On Mon, Oct 31, 2022 at 04:13:38PM -0600, Jeff Law wrote: > >>> >> On 10/30/22 20:42, Jiufu G

[COMMITTED] Implement op[12]_range operators for PLUS_EXPR and MINUS_EXPR.

We can implement the op[12]_range entries for plus and minus in terms of each other. These are adapted from the integer versions. gcc/ChangeLog: * range-op-float.cc (foperator_plus::op1_range): New. (foperator_plus::op2_range): New. (foperator_minus::op1_range): New.

[PATCH (pushed)] sphinx: fix building if sphinx-build is missing

I noticed I modified Makefile.in files in the Sphinx series. While I was supposed to modifiky Makefile.am and use automake. I'm going to fix that soon. Martin libgomp/ChangeLog: * Makefile.in: Build info pages conditionally. libitm/ChangeLog: * Makefile.in: Build info pages con

Re: [RFC] propgation leap over memory copy for struct

Hi, Richard Biener writes: > On Mon, Oct 31, 2022 at 11:14 PM Jeff Law via Gcc-patches > wrote: >> >> >> On 10/30/22 20:42, Jiufu Guo via Gcc-patches wrote: >> > Hi, >> > >> > We know that for struct variable assignment, memory copy may be used. >> > And for memcpy, we may load and store more b

Re: [PATCH] RISC-V: costs: handle BSWAP

On Wed, 9 Nov 2022 at 05:43, Andrew Pinski wrote: > > On Tue, Nov 8, 2022 at 7:16 PM Palmer Dabbelt wrote: > > > > On Tue, 08 Nov 2022 18:57:26 PST (-0800), jeffreya...@gmail.com wrote: > > > > > > On 11/8/22 12:54, Philipp Tomsich wrote: > > >> The BSWAP operation is not handled in rtx_costs. Ad

Re: [PATCH] RISC-V: costs: handle BSWAP

Applied to master, with the commit-message regenerated as: gcc/ChangeLog: * config/riscv/riscv.cc (riscv_rtx_costs): Add BSWAP. Thanks, Philipp. On Wed, 9 Nov 2022 at 04:15, Palmer Dabbelt wrote: > > On Tue, 08 Nov 2022 18:57:26 PST (-0800), jeffreya...@gmail.com wrote: > > > >

Re: [PATCH v2] RISC-V missing __builtin_lceil and __builtin_lfloor

c" .option nopic .text .align 2 .globl x .type x, @function x: fcvt.l.d a0,fa0,rup ret .size x, .-x .ident "GCC: (GNU) 13.0.0 20221109 (experimental)" .section.note.GNU-stack,""

Re: [PATCH] Restore RTL alias analysis for hard frame pointer

> Oh, do you have a testcase suitable for the testsuite? C guality testcase attached, it fails on x86/Linux with -m32 on the gcc-12 branch (which does not have the fix): FAIL: gcc.dg/guality/param-6.c -O1 -DPREVENT_OPTIMIZATION line 15 i == 5 FAIL: gcc.dg/guality/param-6.c -O2 -DPREVENT_O

Re: [PATCH] invoke: RISC-V's -march doesn't take ISA strings

On Wed, Nov 9, 2022 at 4:00 AM Palmer Dabbelt wrote: > On Tue, 08 Nov 2022 05:40:10 PST (-0800), christoph.muell...@vrull.eu > wrote: > > On Mon, Nov 7, 2022 at 8:01 PM Palmer Dabbelt > wrote: > > > >> The docs say we take ISA strings, but that's never really been the case: > >> at a bare minimu

[PATCH (pushed)] avr: sphinx: port gen-avr-mmcu to RST

This ports generation of avr-mcus to RST. Pushed, Martin gcc/ChangeLog: * Makefile.in: Add vpath default for .rst files. * config/avr/avr-devices.cc: For port RST. * config/avr/avr-mcus.def: Update path. * config/avr/gen-avr-mmcu-texi.cc: Moved to... * con

Re: Announcement: Porting the Docs to Sphinx - tomorrow

Hi, On Wed, Nov 09, 2022 at 08:49:22AM +0100, Richard Biener via Gcc wrote: > On Wed, Nov 9, 2022 at 1:09 AM Sam James via Gcc-patches > wrote: > > > On 9 Nov 2022, at 00:00, Joseph Myers wrote: > > > On Tue, 8 Nov 2022, Sam James via Gcc wrote: > > > > If that's your expectation, that's fine, b

Re: [PATCH] invoke: RISC-V's -march doesn't take ISA strings

On Wed, 9 Nov 2022 at 04:00, Palmer Dabbelt wrote: > > On Tue, 08 Nov 2022 05:40:10 PST (-0800), christoph.muell...@vrull.eu wrote: > > On Mon, Nov 7, 2022 at 8:01 PM Palmer Dabbelt wrote: > > > >> The docs say we take ISA strings, but that's never really been the case: > >> at a bare minimum we'

RE: [PATCH 1/4]middle-end Support not decomposing specific divisions during vectorization.

Hi Tamar, > -Original Message- > From: Gcc-patches bounces+kyrylo.tkachov=arm@gcc.gnu.org> On Behalf Of Tamar > Christina via Gcc-patches > Sent: Friday, September 23, 2022 10:33 AM > To: gcc-patches@gcc.gnu.org > Cc: nd ; rguent...@suse.de > Subject: [PATCH 1/4]middle-end Support not

Re: [PATCH] Restore RTL alias analysis for hard frame pointer

> Am 09.11.2022 um 10:49 schrieb Eric Botcazou : > >  >> >> Oh, do you have a testcase suitable for the testsuite? > > C guality testcase attached, it fails on x86/Linux with -m32 on the gcc-12 > branch (which does not have the fix): > > FAIL: gcc.dg/guality/param-6.c -O1 -DPREVENT_OPTI

[PATCH] Fix up foperator_abs::op1_range [PR107569]

Hi! foperator_abs::op1_range works except for the NaN handling, from: [frange] double [-Inf, 1.79769313486231570814527423731704356798070567525844996599e+308 (0x0.f8p+1024)] lhs it computes r [frange] double [-1.79769313486231570814527423731704356798070567525844996599e+308 (-0x0.fff

[DOCS] sphinx: align documentation links with project names

And add missing documentation. Pushed. --- htdocs/onlinedocs/index.html | 160 +++ 1 file changed, 69 insertions(+), 91 deletions(-) diff --git a/htdocs/onlinedocs/index.html b/htdocs/onlinedocs/index.html index a64c9813..cfa8bf5a 100644 --- a/htdocs/onlinedocs/in

[DOCS] sphinx: use new Sphinx links

Pushed. --- htdocs/about.html | 2 +- htdocs/bugs/index.html | 4 ++-- htdocs/faq.html| 6 +++--- htdocs/news.html | 4 ++-- htdocs/projects/beginner.html | 8 htdocs/projects/documentation.html | 2 +- htdocs/

[PATCH 6/12 V2] arm: Add pointer authentication for stack-unwinding runtime

Hi all, please find attached the latest version of this patch now updating the stack pointer value after the pop used to read the PAC value. Best Regards Andrea >From a78acf8804daa3d493b419b4998f4ac705869ff9 Mon Sep 17 00:00:00 2001 From: Andrea Corallo Date: Mon, 6 Dec 2021 11:42:11 +0100 S

Re: [DOCS] sphinx: use new Sphinx links

Gerald, can you please propagate changes I made to: htdocs/style.mhtml file? Thanks, Martin On 11/9/22 12:13, Martin Liška wrote: > Pushed. > > --- > htdocs/about.html | 2 +- > htdocs/bugs/index.html | 4 ++-- > htdocs/faq.html| 6 +++--- > h

Re: [PATCH] Fix up foperator_abs::op1_range [PR107569]

On Wed, Nov 9, 2022 at 11:55 AM Jakub Jelinek wrote: > > Hi! > > foperator_abs::op1_range works except for the NaN handling, > from: > [frange] double [-Inf, > 1.79769313486231570814527423731704356798070567525844996599e+308 > (0x0.f8p+1024)] > lhs it computes r > [frange] double > [

Re: [AArch64] Enable generation of FRINTNZ instructions

On 07/11/2022 14:56, Richard Biener wrote: On Mon, 7 Nov 2022, Andre Vieira (lists) wrote: On 07/11/2022 11:05, Richard Biener wrote: On Fri, 4 Nov 2022, Andre Vieira (lists) wrote: Sorry for the delay, just been reminded I still had this patch outstanding from last stage 1. Hopefully sinc

[PATCH (pushed)] sphinx: update crontab with new script

maintainer-scripts/ChangeLog: * crontab: Use new script for documentation of master branch. --- maintainer-scripts/crontab | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/maintainer-scripts/crontab b/maintainer-scripts/crontab index a961ff1ed5b..09e33c0095f 100644 ---

[PATCH (pushed)] sphinx: update diagnostics URLs

For the future, we'll use https://pypi.org/project/sphinx-redirect-by-id/ which will allow links like https://gcc.gnu.org/onlinedocs/gcc/redirect.html?q=cmdoption-Wfoo but for now, let's use the proper landing pages. Martin gcc/ChangeLog: * opts.cc (get_option_html_page): Port to sphin

Re: [RFC PATCH] c++: Minimal handling of carries_dependency attribute

On Tue, Nov 08, 2022 at 01:40:03PM -1000, Jason Merrill wrote: > > A comment in D2552R1: > > "The only questionable (but still conforming) case we found was > > [[carries_dependency(some_argument)]] on GCC, where the emitted diagnostic > > said that the > > carries_dependency attribute is not supp

[PATCH] AArch64: Add fma_reassoc_width [PR107413]

Add a reassocation width for FMAs in per-CPU tuning structures. Keep the existing setting for cores with 2 FMA pipes, and use 4 for cores with 4 FMA pipes. This improves SPECFP2017 on Neoverse V1 by ~1.5%. Passes regress/bootstrap, OK for commit? gcc/ PR 107413 * config/aarch64/a

[PATCH (pushed)] docs: fix: WARNING: Parsing of expression failed. Using fallback parser.

For the future, we can use https://sphinx-fortran.readthedocs.io/ for Fortran functions which can have optional arguments. However, it's an additional dependency. Simplify the function declration. gcc/fortran/ChangeLog: * doc/gfortran/intrinsic-procedures/aint.rst: Simplify function

Re: [COMMITTED] [range-op-float] Abstract out binary operator code out of PLUS_EXPR entry.

On Wed, Nov 09, 2022 at 08:07:57AM +0100, Aldy Hernandez wrote: > The PLUS_EXPR was always meant to be a template for further > development, since most of the binary operators will share a similar > structure. This patch abstracts out the common bits into the default > definition for range_operato

Re: [RFC] propgation leap over memory copy for struct

On Wed, 9 Nov 2022, Jiufu Guo wrote: > Hi, > > Richard Biener writes: > > > On Mon, Oct 31, 2022 at 11:14 PM Jeff Law via Gcc-patches > > wrote: > >> > >> > >> On 10/30/22 20:42, Jiufu Guo via Gcc-patches wrote: > >> > Hi, > >> > > >> > We know that for struct variable assignment, memory copy

Re: [PATCH (pushed)] sphinx: update diagnostics URLs

On Wed, Nov 9, 2022 at 1:12 PM Martin Liška wrote: > > For the future, we'll use https://pypi.org/project/sphinx-redirect-by-id/ > which will allow links like > > https://gcc.gnu.org/onlinedocs/gcc/redirect.html?q=cmdoption-Wfoo > > but for now, let's use the proper landing pages. Do we need a re

RE: [PATCH] RISC-V: cost model for loading 64bit constant in rv32

>> comparison with clang: >> https://godbolt.org/z/v5nxTbKe9 > > IIUC the rules are generally no compiler explorer links (so we can > preserve history) and no attachment patches (ie, inline them like > git-send-email does). There's some documenation on sending pat

Re: [PATCH (pushed)] sphinx: update diagnostics URLs

On 11/9/22 14:00, Richard Biener wrote: > Do we need a redirect at the old location? Well, what's not working are older gcc releases that still point to "master" branch documentation: gcc --version gcc (SUSE Linux) 12.2.1 20221020 [revision 0aaef83351473e8f4eb774f8f999bbe87a4866d7] ... https://

Re: [COMMITTED] [range-op-float] Abstract out binary operator code out of PLUS_EXPR entry.

On Wed, Nov 9, 2022 at 1:48 PM Jakub Jelinek wrote: > > On Wed, Nov 09, 2022 at 08:07:57AM +0100, Aldy Hernandez wrote: > > The PLUS_EXPR was always meant to be a template for further > > development, since most of the binary operators will share a similar > > structure. This patch abstracts out

Re: [PATCH (pushed)] sphinx: update diagnostics URLs

On Wed, Nov 9, 2022 at 2:07 PM Martin Liška wrote: > > On 11/9/22 14:00, Richard Biener wrote: > > Do we need a redirect at the old location? > > Well, what's not working are older gcc releases that still point to "master" > branch > documentation: > > gcc --version > gcc (SUSE Linux) 12.2.1 2022

Re: [COMMITTED] [range-op-float] Abstract out binary operator code out of PLUS_EXPR entry.

On Wed, Nov 09, 2022 at 02:14:19PM +0100, Aldy Hernandez wrote: > On Wed, Nov 9, 2022 at 1:48 PM Jakub Jelinek wrote: > > > > On Wed, Nov 09, 2022 at 08:07:57AM +0100, Aldy Hernandez wrote: > > > The PLUS_EXPR was always meant to be a template for further > > > development, since most of the binar

[PATCH] changelog: check for space after tab

Will install if there are not comments. Martin contrib/ChangeLog: * gcc-changelog/git_commit.py: Check for a space after leading tab. * gcc-changelog/test_email.py: Likewise. * gcc-changelog/test_patches.txt: Likewise. --- contrib/gcc-changelog/git_commit.py|

Re: [DOCS] sphinx: use new Sphinx links

On 11/9/22 12:22, Martin Liška wrote: > Gerald, can you please propagate changes I made to: > htdocs/style.mhtml file? Gerald I would like to ask you for further server actions related to the Sphinx documentation: 1) https://gcc.gnu.org/install/ - for the future we will use https://gcc.gnu.org/on

Re: [COMMITTED] [range-op-float] Implement MINUS_EXPR.

Hi Aldy, This commit breaks the attached test case at -O2 on x86_64-linux-gnu and loongarch64-linux-gnu :(. The code is simplified from Glibc: the breakage causes two Glibc test failures on loongarch64-linux-gnu. Reverting the commit can fix the breakage. On Wed, 2022-11-09 at 08:07 +0100, Aldy

[PATCH] tree-optimization/84646 - remove premature thread path rejection

This removes a premature rejection that's done later in a different way. Bootstrapped and tested on x86_64-unknown-linux-gnu, pushed. PR tree-optimization/84646 * tree-ssa-threadbackward.cc (back_threader::maybe_register_path): Remove premature cycle rejection. --- gcc/tr

[PATCH v2 0/4] LoongArch: Add some floating-point operations

These patches allow to expand the following builtins to floating point instructions for LoongArch: - __builtin_rint{,f} - __builtin_{l,ll}rint{,f} - __builtin_{l,ll}floor{,f} - __builtin_{l,ll}ceil{,f} - __builtin_scalb{n,ln}{,f} - __builtin_logb{,f} Bootstrapped and regtested on loongarch64-linu

[PATCH v2 1/4] LoongArch: Rename frint_ to rint2

Use standard name so __builtin_rint{,f} can be expanded to one instruction. gcc/ChangeLog: * config/loongarch/loongarch.md (frint_): Rename to .. (rint2): .. this. gcc/testsuite/ChangeLog: * gcc.target/loongarch/frint.c: New test. --- gcc/config/loongarch/loongarch.md

[PATCH v2 3/4] LoongArch: Add fscaleb.{s, d} instructions as ldexp{sf, df}3

This allows optimizing __builtin_ldexp{,f} and __builtin_scalbn{,f} with -fno-math-errno. IMODE is added because we can't hard code SI for operand 2: fscaleb.d instruction always take the high half of both source registers into account. See my_ldexp_long in the test case. gcc/ChangeLog:

[PATCH v2 2/4] LoongArch: Add ftint{,rm,rp}.{w,l}.{s,d} instructions

This allows to optimize the following builtins if -fno-math-errno: - __builtin_lrint{,f} - __builtin_lfloor{,f} - __builtin_lceil{,f} Inspired by https://gcc.gnu.org/pipermail/gcc-patches/2022-November/605287.html. ANYFI is added so the compiler won't try ftint.l.s if -mfpu=32. If we simply use

Re: [PATCH Rust front-end v3 38/46] gccrs: Add HIR to GCC GENERIC lowering entry point

On Wed, Oct 26, 2022 at 10:37 AM wrote: > > From: Philip Herron > > This patch contains the entry point and utilities used for the lowering > of HIR nodes to `tree`s. It also contains a constant evaluator, ported > over from the C++ frontend. > > Co-authored-by: David Faust > Co-authored-by: Fai

[PATCH v2 4/4] LoongArch: Add flogb.{s, d} instructions and expand logb{sf, df}2

On LoongArch, flogb instructions extract the exponent of a non-negative floating point value, but produces NaN for negative values. So we need to add a fabs instruction when we expand logb. gcc/ChangeLog: * config/loongarch/loongarch.md (UNSPEC_FLOGB): New unspec. (type): Add flo

[RFC] docs: remove documentation for unsupported releases

Hi. I think we should remove documentation for unsupported GCC releases as it's indexed by Google engine. Second reason is that the page is long one one can't easily jump to Current development documentation. Thoughts? Martin --- htdocs/onlinedocs/index.html | 1294 -

Re: [COMMITTED] [range-op-float] Implement MINUS_EXPR.

On Wed, 2022-11-09 at 21:49 +0800, Xi Ruoyao wrote: > Hi Aldy, > > This commit breaks the attached test case at -O2 on x86_64-linux-gnu and ^^^ Ah, not this one. I meant r13-3842 "Implement op[12]_range operators for PLUS_EXPR and MINUS_EXPR." > loongarch64-linux-gnu :(. > > The code

Re: [RFC] docs: remove documentation for unsupported releases

On Wed, Nov 09, 2022 at 02:54:48PM +0100, Martin Liška wrote: > I think we should remove documentation for unsupported GCC releases > as it's indexed by Google engine. Second reason is that the page is long > one one can't easily jump to Current development documentation. > > Thoughts? I'd prefer

Re: [RFC] docs: remove documentation for unsupported releases

Hello, On Wed, 9 Nov 2022, Martin Liška wrote: > I think we should remove documentation for unsupported GCC releases > as it's indexed by Google engine. Second reason is that the page is long > one one can't easily jump to Current development documentation. > > Thoughts? I think everything that

Re: [COMMITTED] [range-op-float] Abstract out binary operator code out of PLUS_EXPR entry.

On Wed, Nov 09, 2022 at 02:32:55PM +0100, Jakub Jelinek wrote: > On Wed, Nov 09, 2022 at 02:14:19PM +0100, Aldy Hernandez wrote: > > On Wed, Nov 9, 2022 at 1:48 PM Jakub Jelinek wrote: > > > > > > On Wed, Nov 09, 2022 at 08:07:57AM +0100, Aldy Hernandez wrote: > > > > The PLUS_EXPR was always mean

[GCC][PATCH 13/15, v4] arm: Add support for dwarf debug directives and pseudo hard-register for PAC feature.

Hello, This patch teaches the DWARF support in gcc about RA_AUTH_CODE pseudo hard-register and also updates the ".save", ".cfi_register", ".cfi_offset", ".cfi_restore" directives accordingly. This patch also adds support to emit ".pacspval" directive when "pac ip, lr, sp" instruction in genera

[PATCH (pushed)] docs: fix links pointing to gcc.gnu.org/install

Use https://gcc.gnu.org/onlinedocs/install/ instead. ChangeLog: * configure.ac: Use new install URL. * configure: Regenerate. gcc/ChangeLog: * Makefile.in: Use new install URL. * doc/gcc/gcc-command-options/machine-dependent-options/avr-options.rst: Use i

Re: Announcement: Porting the Docs to Sphinx - 9. November 2022

On 10/20/22 18:43, Joseph Myers wrote: > On Thu, 20 Oct 2022, Martin Liška wrote: > >>> Also, but not strictly part of the release issue: >>> >>> (d) Builds with missing or old Sphinx should work regardless of whether >>> such files are in the source directory - but if they aren't in the source

Re: [COMMITTED] Implement op[12]_range operators for PLUS_EXPR and MINUS_EXPR.

On Wed, Nov 09, 2022 at 10:02:46AM +0100, Aldy Hernandez wrote: > We can implement the op[12]_range entries for plus and minus in terms > of each other. These are adapted from the integer versions. I think for NANs the op[12]_range shouldn't act this way. For the forward binary operations, we hav

[wwwdocs] Add httpd redirects for texinfo trunk docs and for each release series

I've tested that the redirects work on my own httpd server, and have verified that no new sphinx-generated docs match these patterns, and no old texinfo docs fail to match them (except for cases like index.html where a new file exists with the same name anyway so we don't need a redirect). For exa

Re: [COMMITTED] Implement op[12]_range operators for PLUS_EXPR and MINUS_EXPR.

On Wed, Nov 9, 2022 at 3:58 PM Jakub Jelinek wrote: > > On Wed, Nov 09, 2022 at 10:02:46AM +0100, Aldy Hernandez wrote: > > We can implement the op[12]_range entries for plus and minus in terms > > of each other. These are adapted from the integer versions. > > I think for NANs the op[12]_range s

Re: [COMMITTED] [range-op-float] Implement MINUS_EXPR.

I have reverted the patch while I sort this out. Thanks for the report and especially for the distilled test. It's very useful. Aldy On Wed, Nov 9, 2022 at 2:58 PM Xi Ruoyao wrote: > > On Wed, 2022-11-09 at 21:49 +0800, Xi Ruoyao wrote: > > Hi Aldy, > > > > This commit breaks the attached test

Re: [COMMITTED] Implement op[12]_range operators for PLUS_EXPR and MINUS_EXPR.

On Wed, Nov 09, 2022 at 04:43:56PM +0100, Aldy Hernandez wrote: > Heh. I just ran into this while debugging the problem reported by Xi. > > We are solving NAN = op1 - VARYING, and trying to do it with op1 = NAN > + VARYING, which returns op1 = NAN (incorrectly). > > I suppose in the above case o

RE: [PATCH 2/4]AArch64 Add implementation for pow2 bitmask division.

Hi Tamar, > -Original Message- > From: Tamar Christina > Sent: Monday, October 31, 2022 11:35 AM > To: Tamar Christina ; gcc-patches@gcc.gnu.org > Cc: nd ; Richard Earnshaw ; > Marcus Shawcroft ; Kyrylo Tkachov > ; Richard Sandiford > > Subject: RE: [PATCH 2/4]AArch64 Add implementation

Re: [PATCH 1/2] Change the name of array_at_struct_end_p to array_ref_flexible_size_p

Thanks. Committed as: https://gcc.gnu.org/pipermail/gcc-cvs/2022-November/373830.html Qing > On Nov 9, 2022, at 2:57 AM, Richard Biener wrote: > > On Tue, 8 Nov 2022, Qing Zhao wrote: > >> The name of the utility routine "array_at_struct_end_p" is misleading >> and should be changed to a new

Re: Announcement: Porting the Docs to Sphinx - tomorrow

On Wed, 9 Nov 2022, Richard Biener via Gcc wrote: > I'd say that doing a trunk snapshot build every day as CI would be nice, we > can then publish one once a week, skipping days where the build failed. Note that each snapshot should have diffs relative to the previous published snapshot. Not re

Re: Announcement: Porting the Docs to Sphinx - 9. November 2022

On Wed, 9 Nov 2022, Martin Liška wrote: > 1) not synchronized content among lib*/Makefile.in and lib*/Makefile.am. > Apparently, I modified the generated Makefile.in file with the rules like: > > doc/info/texinfo/libitm.info: $(SPHINX_FILES) > + if [ x$(HAS_SPHINX_BUILD) = xhas-sphinx-build

Re: Announcement: Porting the Docs to Sphinx - tomorrow

On Wed, Nov 9, 2022 at 6:11 PM Joseph Myers wrote: > > On Wed, 9 Nov 2022, Richard Biener via Gcc wrote: > > > I'd say that doing a trunk snapshot build every day as CI would be nice, we > > can then publish one once a week, skipping days where the build failed. > > Note that each snapshot should

Re: [PATCH] riscv: implement TARGET_MODE_REP_EXTENDED

On Wed, 9 Nov 2022, Philipp Tomsich wrote: > > To give a specific example that will be problematic if you go far enough > > down > > the road of matching MIPS64 behavior: > > > > long f(void) > > { > > int x; > > asm("" : "=r"(x)); > > return x; > > } > > > > here GCC (unlike LLVM) om

[COMMITTED] Clear NAN when reading back a global range if necessary.

When reading back from the global store, we must clear the NAN bit if necessary. The reason it's not happening is because the constructor sets a NAN by default (when HONOR_NANS). We must be careful to clear the NAN bit if the original range didn't have a NAN. I have commented the reason we use t

Re: [PATCH V2] Enable small loop unrolling for O2

> This patch does not change rs6000/s390 since I don't have machines to > test them, but I suppose the default behavior is the same since they > enable flag_unroll_loops at O2. There are Power (rs6000) systems in the Compile Farm. Trial Linux on Z (s390x) VMs are available through the Linux Commu

[PATCH (pushed)] docs: create sources tarball

maintainer-scripts/ChangeLog: * update_web_docs_git.py: Create sources tarball. --- maintainer-scripts/update_web_docs_git.py | 29 +++ 1 file changed, 29 insertions(+) diff --git a/maintainer-scripts/update_web_docs_git.py b/maintainer-scripts/update_web_docs_git.py

[PATCH (pushed)] Include docs-sources in onlinedocs.

--- htdocs/onlinedocs/index.html | 1 + 1 file changed, 1 insertion(+) diff --git a/htdocs/onlinedocs/index.html b/htdocs/onlinedocs/index.html index cfa8bf5a..3410f731 100644 --- a/htdocs/onlinedocs/index.html +++ b/htdocs/onlinedocs/index.html @@ -1610,6 +1610,7 @@ existing release. (htt

Re: [Patch Arm] Fix PR 92999

Hi Ramana, On 08/11/2022 18:20, Ramana Radhakrishnan via Gcc-patches wrote: > PR92999 is a case where the VFP calling convention does not allocate > enough FP registers for a homogenous aggregate containing FP16 values. > I believe this is the complete fix but would appreciate another set of > eye

Re: [RFC] docs: remove documentation for unsupported releases

On Wed, 9 Nov 2022, Michael Matz via Gcc-patches wrote: > I think everything that's on the web server (even the 2.95 docu) has to be > reachable via a (reasonable) set of clicks from the main index.html. It > doesn't need to be _directly_ from the main index.html, though. > > Also, you simply

[PATCH 1/2] symtab: also change RTL decl name

We were changing the ASSEMBLER_NAME of the function decl but not the name in DECL_RTL which is used as the function name fnname in rest_of_handle_final(). This led to using the old, wrong name for the attribute target default function when using target_clones. Bootstrapped and regtested cleanly on

[PATCH 2/2] Fortran: add attribute target_clones

Hi! Add support for attribute target_clones: !GCC$ ATTRIBUTES target_clones("arch1", "arch3","default") :: mysubroutine Bootstrapped and regtested on x86_64-unknown-linux with --target_board=unix'{-m32,-m64}'. OK for trunk? gcc/fortran/ChangeLog: * decl.cc: Include fold-const.h for size

[PATCH 0/2] Fortran: add attribute target_clones

Hi! These two patches add support for attribute target_clones to the fortran frontend. 1) The symtab hunk is identical to the one sent in https://gcc.gnu.org/pipermail/gcc-patches/2022-November/605081.html which had some additional information. I only tested it on x86_64-unknown-linux and for lan

Re: [RFC] docs: remove documentation for unsupported releases

On Wed, 9 Nov 2022, Martin Liška wrote: > Hi. > > I think we should remove documentation for unsupported GCC releases > as it's indexed by Google engine. I'd agree with previous responses that outright removing the links is undesirable, and pointing Google to recent documentation should be done

[PATCH (pushed)] sphinx: add missing HAS_SPHINX_BUILD

libgomp/ChangeLog: * Makefile.in: Add missing HAS_SPHINX_BUILD. libitm/ChangeLog: * Makefile.in: Add missing HAS_SPHINX_BUILD. libquadmath/ChangeLog: * Makefile.in: Add missing HAS_SPHINX_BUILD. --- libgomp/Makefile.in | 1 + libitm/Makefile.in | 1 + libquadm

Re: [RFC] docs: remove documentation for unsupported releases

On 11/9/22 20:32, Alexander Monakov wrote: > > On Wed, 9 Nov 2022, Martin Liška wrote: > >> Hi. >> >> I think we should remove documentation for unsupported GCC releases >> as it's indexed by Google engine. > > I'd agree with previous responses that outright removing the links is > undesirable,

[PATCH (pushed)] docs: Fix expected diagnostics URL [PR107599]

PR c++/107599 gcc/testsuite/ChangeLog: * c-c++-common/diagnostic-format-json-2.c: Fix expected URL. * c-c++-common/diagnostic-format-json-3.c: Likewise. * c-c++-common/diagnostic-format-json-4.c: Likewise. * gfortran.dg/diagnostic-format-json-2.F90: Likewis

[Ping 2][PATCH] Add condition coverage profiling

On 02/11/2022 07:16, Jørgen Kvalsvik wrote: > On 25/10/2022 08:33, Jørgen Kvalsvik wrote: >> On 12/10/2022 12:16, Jørgen Kvalsvik wrote: >>> This patch adds support in gcc+gcov for modified condition/decision >>> coverage (MC/DC) with the -fprofile-conditions flag. MC/DC is a type of >>> test/code

[PATCH, committed] Fortran: avoid NULL pointer dereference on bad EQUIVALENCEs [PR107559]

Dear all, I've committed an obvious patch for NULL pointer dereferences that could occur when checking EQUIVALENCEs. See also attached. Testcase by Gerhard. Regtested on x86_64-pc-linux-gnu. Pushed: https://gcc.gnu.org/g:e505f7493bed1395d121d2f53137ec11706fa42e Thanks, Harald From e505f7493b

Proxy ping [PATCH] Fortran: diagnostics for actual arguments to pointer dummy arguments [PR94104]

Dear all, Jose posted a patch here that was never reviewed: https://gcc.gnu.org/pipermail/fortran/2021-June/056162.html I think the diagnostics improvement is helpful, as it adjusts to the changes from F2003 to F2008. The patch suffered a little from bitrot, but was otherwise straightforward

[PATCH] c++: P2448 - Relaxing some constexpr restrictions [PR106649]

This patch implements C++23 P2448, which lifts more restrictions on the constexpr keyword. It's effectively going the way of being just a hint (hello, inline!). This gist is relatively simple: in C++23, a constexpr function's return type/parameter type doesn't have to be a literal type; and you c

Re: [committed] wwwdocs: codingconventions: Properly link to flake8

On 11/1/22 13:01, Gerald Pfeifer wrote: > Nearly all hrefs= on our site are https:// or http://, and that's the case > pretty much across the web. Still the protocol needs to be provided for > links to work. Makes sense, thanks! Martin > > Pushed. > > Gerald > > > Web links need to be pref

Re: [PATCH] Fix doc typo

On 11/9/22 08:51, Richard Biener via Gcc-patches wrote: > On Wed, Nov 9, 2022 at 4:29 AM Sinan via Gcc-patches > wrote: >> >> add a missing variable name. > > OK. I've just pushed the change. Martin

Re: [PATCH] match.pd: rewrite select to branchless expression

Richard, Thanks for your feedback. I want to make sure I am following what you are recommending. Are you suggesting changing: (for op (bit_xor bit_ior) (simplify (cond (eq (bit_and @0 integer_onep@1) integer_zerop) @2 (op:c @3 @2)) (if (INTEGRAL_TYPE_P (type) && (INTEGRAL_TYPE_P (TREE_TYPE (@0

[PATCH] doc: Use a separate directory for new modules we add to PATH

ChangeLog: * doc/baseconf.py: Inject dirname(__file__)/'modules' to path instead of just ``.''. * doc/gcc_sphinx.py: Moved to... * doc/modules/gcc_sphinx.py: ...here. --- Evening, This patch addresses a path mixup and provides a nice compromise between convenience

[PATCH v2] doc: Remove outdated reference to "core" and front-end downloads

Patch rebased on the new doc format. I haven't tested building the docs this way, but this is just plain text here. OK for trunk? -- >8 -- gcc/ChangeLog: * doc/install/testing.rst: Remove anachronism about separate source tarballs. --- gcc/doc/install/testing.rst | 4 +--- 1 fi

Re: [DOCS] sphinx: use new Sphinx links

On Wed, 9 Nov 2022, Martin Liška wrote: > Gerald, can you please propagate changes I made to: > htdocs/style.mhtml file? Done. All pages live on gcc.gnu.org should be udpated now. (I'm at a conference and have been offline during daytime this week so far. If you want to run further changes, Frid

Re: [PATCH] doc: Use a separate directory for new modules we add to PATH

On Wed, 2022-11-09 at 22:31 +0100, Arsen Arsenović via Gcc-patches wrote: > ChangeLog: > > * doc/baseconf.py: Inject dirname(__file__)/'modules' to path > instead of just ``.''. > * doc/gcc_sphinx.py: Moved to... > * doc/modules/gcc_sphinx.py: ...here. > --- > Eveni

[committed] analyzer: better logging of event creation

Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu. Pushed to trunk as r13-3867-g965ce1ba392ca0. gcc/analyzer/ChangeLog: * checker-path.cc (checker_event::debug): New. (checker_path::add_event): Move here from checker-path.h. Add logging. * checker-path.

[PATCH] RISC-V: Optimise adding a (larger than simm12) constant

Handling the register-const_int addition has very quickly escalated to creating a full sign-extended 32bit constant and performing a register-register for RISC-V in GCC so far, resulting in sequences like (for the case of "a + 2048"): li a5,4096 addia5,a5,-2048 add

[PATCH] RISC-V: Implement movmisalign to enable SLP

The default implementation of support_vector_misalignment() checks whether movmisalign is present for the requested mode. This will be used by vect_supportable_dr_alignment() to determine whether a misaligned access of vectorized data is permissible. For RISC-V this is required to convert multipl

[PATCH] ifcombine: recognize single bit test of sign-bit

Our ifcombine pass combines 2 single-bit tests into a single test of the form "(a & T) == T". However, detection of the bit-tests does not work for sign-bits (of any mode) as the RTL presented to the pass uses a cast to a signed-type and an order-operator. E.g., the test for 'a & 0x80' presents a

[PATCH] ifcombine: fold two bit tests with different polarity

Our ifcombine pass combines 2 single-bit tests into a single test of the form "(a & T) == T", requiring the same polarity (i.e., tests for bit set/cleared) for both bit-tests. However some applications test against two bits expecting one set and the other cleared. This adds support for the case "

[PATCH v2] [WIP] RISC-V: Replace zero_extendsidi2_shifted with generalized split

The current method of treating shifts of extended values on RISC-V frequently causes sequences of 3 shifts, despite the presence of the 'zero_extendsidi2_shifted' pattern. Consider: unsigned long f(unsigned int a, unsigned long b) { a = a << 1; unsigned long c = (un

  1   2   >