Re: [PATCH] middle-end/100951 - make sure to generate VECTOR_CST in lowering

On Wed, Jun 9, 2021 at 2:03 PM Jeff Law wrote: > > > > On 6/7/2021 2:33 PM, H.J. Lu via Gcc-patches wrote: > > On Mon, Jun 7, 2021 at 11:10 AM Richard Biener > wrote: > > On Mon, Jun 7, 2021 at 7:59 PM Richard Biener > wrote: > > On Mon, Jun 7, 2021 at 4:19 PM H.J. Lu wrote: > > On Mon, Jun 7,

Re: [patch] Reuse non-gimple_reg variable for inlining

> I'm afraid the inliner would need to prove the to be inlined callee doesn't > modify its own copy of the variable too, because if it modifies it (at least > in C/C++ const can be cast away), then this introduces wrong-code, see > PR100994 for details. Then please remove the TREE_READONLY marker

Re: [PATCH] rs6000: Add new __builtin_vsx_build_pair and __builtin_mma_build_acc built-ins

Hi! On Wed, Jun 09, 2021 at 04:05:37PM -0500, Peter Bergner wrote: > The __builtin_vsx_assemble_pair and __builtin_mma_assemble_acc built-ins > currently assign their first source operand to the first VSX register > in a pair/quad, their second operand to the second register in a pair/quad, > etc

[PATCH] PR fortran/100950 - ICE in output_constructor_regular_field, at varasm.c:5514

Dear Fortranners, we should be able to simplify the length of a substring with known constant bounds. The attached patch adds this. Regtested on x86_64-pc-linux-gnu. OK for mainline? Since this should be rather safe, to at least 11-branch? Thanks, Harald Fortran - simplify length of substri

[committed] analyzer: make various region_model member functions const

Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu. Pushed to trunk as 53cb324cb4f9475d4eabcd9f5a858c5edaacc0cf. gcc/analyzer/ChangeLog: * region-model.cc (region_model::get_lvalue_1): Make const. (region_model::get_lvalue): Likewise. (region_model::get_rvalue_1)

Re: [r12-1330 Regression] FAIL: libgomp.fortran/pr100981-2.f90 -Os execution test on Linux/x86_64

On Wed, Jun 09, 2021 at 12:08:39PM -0700, sunil.k.pandey via Gcc-patches wrote: > On Linux/x86_64, > > 374f93da97fb0378453d503f3cfea4d7a923a89c is the first bad commit > commit 374f93da97fb0378453d503f3cfea4d7a923a89c > Author: Richard Biener > Date: Wed Jun 9 14:48:35 2021 +0200 > > tree-

Re: [PATCH] rs6000: Support more short/char to float conversion

Hi! On Fri, May 07, 2021 at 10:30:38AM +0800, Kewen.Lin wrote: > For some cases that when we load unsigned char/short values from > the appropriate unsigned char/short memories and convert them to > double/single precision floating point value, there would be > implicit conversions to int first.

Re: [PATCH v3 2/2] x86: Add vec_duplicate expander

On Tue, Jun 8, 2021 at 11:41 PM Uros Bizjak wrote: > > On Tue, Jun 8, 2021 at 7:59 PM H.J. Lu wrote: > > > > 1. Update vec_duplicate to allow to fail so that backend can only allow > > broadcasting an integer constant to a vector when broadcast instruction > > is available. This can be used by m

Re: [PATCH v3 1/2] x86: Convert CONST_WIDE_INT/CONST_VECTOR to broadcast

On Wed, Jun 9, 2021 at 12:44 AM Uros Bizjak wrote: > > [For some reason this message didn't reach my gmail account] > > > 1. Update move expanders to convert the CONST_WIDE_INT and CONST_VECTO > > operands to vector broadcast from an integer with AVX2. > > 2. Add ix86_gen_scratch_sse_rtx to return

[PATCH v4 2/2] x86: Add vec_duplicate expander

1. Update vec_duplicate to allow to fail so that backend can only allow broadcasting an integer constant to a vector when broadcast instruction is available. This can be used by memset expander to avoid vec_duplicate when loading from constant pool is more efficient. 2. Add vec_duplicate expander

[PATCH v4 0/2] x86: Convert CONST_WIDE_INT/CONST_VECTOR to broadcast

1. Update move expanders to convert the CONST_WIDE_INT and CONST_VECTO operands to vector broadcast from an integer with AVX2. 2. Add ix86_gen_scratch_sse_rtx to return a scratch SSE register which won't increase stack alignment requirement and blocks transformation by the combine pass. A small be

[PATCH v4 1/2] x86: Convert CONST_WIDE_INT/CONST_VECTOR to broadcast

1. Update move expanders to convert the CONST_WIDE_INT and CONST_VECTO operands to vector broadcast from an integer with AVX2. 2. Add ix86_gen_scratch_sse_rtx to return a scratch SSE register which won't increase stack alignment requirement and blocks transformation by the combine pass. A small be

Re: [PATCH v4 2/2] x86: Add vec_duplicate expander

On Wed, Jun 9, 2021 at 4:39 PM H.J. Lu wrote: > > 1. Update vec_duplicate to allow to fail so that backend can only allow > broadcasting an integer constant to a vector when broadcast instruction > is available. This can be used by memset expander to avoid vec_duplicate > when loading from consta

[PATCH] c++: Extend std::is_constant_evaluated in if warning [PR100995]

Jakub pointed me at which shows that our existing warning could be extended to handle more cases. This patch implements that. A minor annoyance was handling macros, in libstdc++ we have reference operator[

git gcc-commit-mklog doesn't extract PR number to ChangeLog

Hi, I noticed that the "git gcc-commit-mklog" command doesn't extract PR number from title to ChangeLog automatically, then the committed patch doesn't update the related bugzilla PR website after check in the patch? Martin, what's your opinion about this since you are much familar about this? Than

Re: [PATCH] PR tree-optimization/100781 - Do not calculate new values when evaluating a debug, statement.

On Wed, Jun 9, 2021 at 5:24 PM Andrew MacLeod wrote: > > On 6/9/21 7:48 AM, Richard Biener wrote: > > On Tue, Jun 8, 2021 at 4:48 PM Andrew MacLeod wrote: > >> > >> > >> Richard. > >> > Andrew > > >> OK, so this would be the simple way I'd tackle this in gcc11. This > >> should be quite

Re: [patch] Reuse non-gimple_reg variable for inlining

On Wed, 9 Jun 2021, Eric Botcazou wrote: > > I'm afraid the inliner would need to prove the to be inlined callee doesn't > > modify its own copy of the variable too, because if it modifies it (at least > > in C/C++ const can be cast away), then this introduces wrong-code, see > > PR100994 for deta

Re: [r12-1330 Regression] FAIL: libgomp.fortran/pr100981-2.f90 -Os execution test on Linux/x86_64

On Thu, 10 Jun 2021, Jakub Jelinek wrote: > On Wed, Jun 09, 2021 at 12:08:39PM -0700, sunil.k.pandey via Gcc-patches > wrote: > > On Linux/x86_64, > > > > 374f93da97fb0378453d503f3cfea4d7a923a89c is the first bad commit > > commit 374f93da97fb0378453d503f3cfea4d7a923a89c > > Author: Richard Bien

<    1   2