lowpart_subreg might fail in some cases when trying to create paradoxical
SUBREGs. Use force_reg on input operand, use new temporary output operand
and emit move into the destination afterwards.
Also, replace simplify_gen_subreg (Mx, op, My, 0)
with equivalent lowpart_subreg (Mx, op, My).
2021-1
Hi,
> Did you mean to include the change pruning visibility warnings? I don't
> think it's necessarily wrong, it just doesn't match the patch description or
> ChangeLog.
Yes, I think they should be applied, and will fix long-standing failures
reported in https://gcc.gnu.org/bugzilla/show_bug.
Hi,
When TARGET_AVOID_XFORM is set, we turn off VSX. But at least from
ISA3.0 (Power9), we support DQ form vector load/store. This patch
is to make it not clear VSX when P9 VECTOR supported, it also checks
some flags which P9 VECTOR relies on, otherwise those flags could
disable P9 VECTOR later.
Hi,
Option -mpower10 was made as "WarnRemoved" since commit r11-2318,
so -mno-power10 doesn't take effect any more. This patch is to
remove one line useless code which still respects it.
Bootstrapped and regtested on powerpc64le-linux-gnu P9 and
powerpc64-linux-gnu P8.
Is it ok for trunk?
BR,
Hi!
The following testcases ICE when an optimize or target pragma
is followed by a long line (4096+ chars).
This is because on such long lines we can't use columns anymore,
but the cpp_define calls performed by c_cpp_builtins_optimize_pragma
or from the backend hooks for target pragma are done on
Hi!
make_forwarders_with_degenerate_phis causes a -fcompare-debug failure on the
following testcase.
The problem is that on:
# iftmp.4_8 = PHI <&D.2582(6), &D.2583(4), &D.2582(7), &D.2583(5)>
the exact DECL_UIDs are different between -g and -g0 (which is ok, with -g
the decls can have larger gap
Hi!
The r12-5978 change caused a -fcompare-debug issue, because without
-g a chain might start with a noop move, but with -g there could be
one or more DEBUG_INSNs in the chain before the noop move and so
regrename could make different decisions between -g and -g0.
Note, I must say I don't really
Hi!
We get a -fcompare-debug FAIL on the following testcase. The problem is
that during cprop we get when a TImode pseudo holding x is being
constructed:
(debug_insn 111 59 103 7 (var_location:TI D#2 (clobber (const_int 0 [0]))) -1
(nil))
(insn 103 111 110 7 (clobber (reg/v:TI 89 [ x ])) "pr
Hi Harald,
That is the sort of thing that I had in mind. Is it worth adding the check
for CLASS_DATA? I cannot remember if that is made redundant by the test of
the class_ok attribute.
Cheers
Paul
On Tue, 28 Dec 2021 at 21:08, Harald Anlauf wrote:
> Hi Paul,
>
> Am 28.12.21 um 12:56 schrieb
> >
> > From: Xiong Hu Luo
> >
> > gcc/ChangeLog:
> >
> > * loop-invariant.c (find_invariants_bb): Check profile count
> > before motion.
> > (find_invariants_body): Add argument.
> >
> > gcc/testsuite/ChangeLog:
> >
> > * gcc.dg/loop-invariant-2.c: New.
OK,
thanks!
Honza
Hi Richard,
Thank you for the review, I've adopted all above suggestions downstream,
I am still surprised how many style things I still miss after years of
gcc development :(
On 17/12/2021 12:44, Richard Sandiford wrote:
@@ -3252,16 +3257,31 @@ vectorizable_call (vec_info *vinfo,
r
"Andre Vieira (lists)" writes:
> On 17/12/2021 12:44, Richard Sandiford wrote:
>>
>>> @@ -3252,16 +3257,31 @@ vectorizable_call (vec_info *vinfo,
>>> rhs_type = unsigned_type_node;
>>> }
>>>
>>> - int mask_opno = -1;
>>> + /* The argument that is not of the same type as the othe
Hi Paul,
Am 29.12.21 um 12:45 schrieb Paul Richard Thomas via Fortran:
Hi Harald,
That is the sort of thing that I had in mind. Is it worth adding the check
for CLASS_DATA? I cannot remember if that is made redundant by the test of
the class_ok attribute.
the macro CLASS_DATA appears to have
On 12/29/2021 2:13 AM, FX wrote:
Hi,
Did you mean to include the change pruning visibility warnings? I don't think
it's necessarily wrong, it just doesn't match the patch description or
ChangeLog.
Yes, I think they should be applied, and will fix long-standing failures
reported in https
On December 29, 2021 11:11:18 AM GMT+01:00, Jakub Jelinek
wrote:
>Hi!
>
>make_forwarders_with_degenerate_phis causes a -fcompare-debug failure on the
>following testcase.
>The problem is that on:
> # iftmp.4_8 = PHI <&D.2582(6), &D.2583(4), &D.2582(7), &D.2583(5)>
>the exact DECL_UIDs are differ
Hi,
Fortran 2018 added some synonyms to the existing IEEE_CLASS_TYPE values, namely
IEEE_NEGATIVE_SUBNORMAL (which is the same as IEEE_NEGATIVE_DENORMAL)
and IEEE_POSITIVE_SUBNORMAL (same as IEEE_POSITIVE_DENORMAL). When they
were added to the C side, they were not kept in sync with the Fortran
pa
I realized that trying to do an assignment to an array created by the
new array constructor API will result in a "gimplification failed"
error:
libgccjit.so: error: gimplification failed
0x7fa3a441e5d3 gimplify_expr(tree_node**, gimple**, gimple**, bool
(*)(tree_node*), int)
../../../gcc/g
This patch to the Go frontend, libgo, and the -fgo-dump-spec code
avoids padding incorrectly when a zero-sized field is inserted solely
for alignment. We avoid this by not padding after a "_" field, and by
using "_" fields for padding. This is fine since the padding is only
there in case someone
Could you be more specific? I tried the equivalent of:
/*int [50] foobar = {1,2,3,4};
int [50] foo() { int arr[50];
arr = (int [50]){-1,-2,-3,-4,-5,-6};
arr = foobar;
arr = (int [50]){1,2,3,4,5,6};
Oh, sorry, I meant when you have an array not in a local variable, and
you try to assign to an index of this array.
Something like:
gcc_jit_rvalue *ctor = gcc_jit_context_new_array_constructor
(ctxt,0,int50arr_type,6,values);
gcc_jit_block_add_assignment (block, 0,
gcc_jit_context_new_arra
From: LiaoShihua
following 'false' branch in line 20, 'tmp.word_state' leaks in line 26. So
free 'tmp.word_state' before return 'rval'.
gcc/testsuite\ChangeLog:
* gcc.dg/analyzer/pr103526.c:
---
gcc/testsuite/gcc.dg/analyzer/pr103526.c | 3 ++-
1 file changed, 2 insertions(+),
Add -msmall-data-limit option to put global and static data into right
section and generate 'btt_info' on RISC-V target.
BTF (BPF Type Format) is the metadata format which encodes the debug info
related to BPF program/map, more details on:
https://www.kernel.org/doc/html/latest/bpf/index.html#bpf
From: LiaoShihua
* gcc.dg/pr102892-2.c: Add definition of function foo() which declared
in pr102892-1.c
---
gcc/testsuite/gcc.dg/pr102892-2.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/gcc/testsuite/gcc.dg/pr102892-2.c
b/gcc/testsuite/gcc.dg/pr102892-2.c
index b39bd6c97b3
On Wed, Dec 29, 2021 at 9:39 PM wrote:
>
> From: LiaoShihua
>
> * gcc.dg/pr102892-2.c: Add definition of function foo() which
> declared in pr102892-1.c
This patch is wrong. The testcase is testing to make sure foo was
optimized out. If it is failing for you can you file a bug with the
On 2021/12/29 20:55, Jan Hubicka wrote:
>>>
>>> From: Xiong Hu Luo
>>>
>>> gcc/ChangeLog:
>>>
>>> * loop-invariant.c (find_invariants_bb): Check profile count
>>> before motion.
>>> (find_invariants_body): Add argument.
>>>
>>> gcc/testsuite/ChangeLog:
>>>
>>> * gcc.dg/loop-inva
25 matches
Mail list logo
