On 26.11.23 12:18, haochen.jiang wrote:
On Linux/x86_64,
20a3c74c347429c109bc7002285b735be83f6a0b is the first bad commit
commit 20a3c74c347429c109bc7002285b735be83f6a0b
Author: Sebastian Huber
Date: Tue Nov 14 21:36:51 2023 +0100
gcov: Improve -fprofile-update=atomic
caused
FAIL:
On 26.11.23 12:18, haochen.jiang wrote:
On Linux/x86_64,
a350a74d6113e3a84943266eb691275951c109d9 is the first bad commit
commit a350a74d6113e3a84943266eb691275951c109d9
Author: Sebastian Huber
Date: Sat Oct 21 15:52:15 2023 +0200
gcov: Add gen_counter_update()
caused
FAIL:
> On Sat, Nov 25, 2023 at 12:03:56PM +, Tamar Christina wrote:
> > For the C99 versions of copysign, expand_COPYSIGN has optimized
> expansions inplace.
> > One of the hooks there forces it to abs/neg. There is also code in
> > place for if the target prefers integer expansion over floating
On Sun, 26 Nov 2023, Martin Uecker wrote:
>
> Thanks Joseph, I will sent an updated series tomorrow.
>
> Richard, maybe you could look at what I wrote below
> about my use of TYPE_CANONICAL ? Does this make sense?
>
>
> Am Donnerstag, dem 23.11.2023 um 23:47 + schrieb Joseph Myers:
> >
Jakub Jelinek 于2023年11月24日周五 23:54写道：
>
> Hi!
>
> As reported in the PR, mipsisa64r2-sde-elf doesn't build because
> HEAP_TRAMPOLINES_INIT
> macro isn't defined anywhere.
> It is normally defined by
> # Figure out if we need to enable heap trampolines by default
> case ${target} in
>
Now that we are finally able to use the kernel provided bpf_helpers.h
file and associated machinery, there is no longer need to distribute
our own version.
This patch removes bpf-helpers.h and deletes most of the associated
tests from the gcc.target/bpf testsuite. Two tests are adapted and
On 11/24/23 03:18, Tsukasa OI wrote:
From: Tsukasa OI
Along with RV32E, RV64E is ratified. Though ILP32E and LP64E ABIs are
still draft, it's worth supporting it.
gcc/ChangeLog:
* common/config/riscv/riscv-common.cc
(riscv_ext_version_table): Set version to ratified 2.0.
On Thu, Nov 23, 2023 at 03:03:37PM -0500, Nathan Sidwell wrote:
> On 11/20/23 04:47, Nathaniel Shead wrote:
> > Bootstrapped and regtested on x86_64-pc-linux-gnu. I don't have write
> > access.
> >
> > -- >8 --
> >
> > Block-scope declarations of functions or extern values are not allowed
> >
Ping ^3!
Thanks & Regards
Ajit
Forwarded Message
Subject: [PING ^3][PATCH v2] rs6000: Add new pass for replacement of contiguous
addresses vector load lxv with lxvp
Date: Mon, 27 Nov 2023 10:15:26 +0530
From: Ajit Agarwal
To: Kewen.Lin , Segher Boessenkool
, Peter Bergner
Ping^2!
Forwarded Message
Subject: [PING ^1] [PATCH v2 3/4] Improve functionality of ree pass with
various constants with AND operation.
Date: Fri, 10 Nov 2023 12:39:02 +0530
From: Ajit Agarwal
To: gcc-patches
CC: Jeff Law , Vineet Gupta ,
Richard Biener , Segher
Ping ^2!
Ok for trunk?
Thanks & Regards
Ajit
Forwarded Message
Subject: [PING][PATCH V15 4/4] ree: Improve ree pass using defined abi
interfaces
Date: Fri, 10 Nov 2023 12:37:25 +0530
From: Ajit Agarwal
To: Vineet Gupta , Jeff Law ,
Bernhard Reutner-Fischer
CC: Richard
While looking into PR 112454, I found the cost for
`(if_then_else (cmp) (const_int 1) (reg))` was being recorded as 8
(or `COSTS_N_INSNS (2)`) but it should have been 4 (or `COSTS_N_INSNS (1)`).
This improves the cost by not adding the cost of `(const_int 1)` to
the total cost.
It does not does
Hi,
"Kewen.Lin" writes:
> Hi,
>
> on 2023/11/15 11:02, Jiufu Guo wrote:
>> Hi,
>>
>> Trunk gcc supports more constants to be built via two instructions: e.g.
>> "li/lis; xori/xoris/rldicl/rldicr/rldic".
>> And then num_insns_constant should also be updated.
>>
>> Function
Pushed to r14-5864.
在 2023/11/23 上午11:05, Guo Jie 写道:
gcc/ChangeLog:
* config/loongarch/loongarch.cc (loongarch_split_plus_constant):
avoid left shift of negative value -0x8000.
---
gcc/config/loongarch/loongarch.cc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On Linux/x86_64,
53ba8d669550d3a1f809048428b97ca607f95cf5 is the first bad commit
commit 53ba8d669550d3a1f809048428b97ca607f95cf5
Author: Jan Hubicka
Date: Mon Nov 20 19:35:53 2023 +0100
inter-procedural value range propagation
caused
FAIL: gcc.dg/guality/ipa-sra-1.c -O2
On Linux/x86_64,
b42a09b258c3ed8d1368e0ef0948034dcf0f8ac9 is the first bad commit
commit b42a09b258c3ed8d1368e0ef0948034dcf0f8ac9
Author: Uros Bizjak
Date: Tue Nov 14 18:34:43 2023 +0100
i386: Generate strict_low_part QImode insn with high input register
caused
FAIL:
On Linux/x86_64,
0a140730c970870a5125beb1114f6c01679a040e is the first bad commit
commit 0a140730c970870a5125beb1114f6c01679a040e
Author: Roger Sayle
Date: Mon Nov 13 09:05:16 2023 +
i386: Improve reg pressure of double word right shift then truncate.
caused
FAIL:
On Linux/x86_64,
a350a74d6113e3a84943266eb691275951c109d9 is the first bad commit
commit a350a74d6113e3a84943266eb691275951c109d9
Author: Sebastian Huber
Date: Sat Oct 21 15:52:15 2023 +0200
gcov: Add gen_counter_update()
caused
FAIL: gcc.dg/gomp/pr27573.c (internal compiler error:
On Linux/x86_64,
aed00696a01ac065e9ed327434ec29d1cf50179e is the first bad commit
commit aed00696a01ac065e9ed327434ec29d1cf50179e
Author: Andre Vieira
Date: Fri Nov 3 19:09:07 2023 +
vect: allow using inbranch simdclones for masked loops
caused
FAIL: gcc.dg/vect/vect-simd-clone-20.c
On Linux/x86_64,
1d82fc2e6824bf83159389729c31a942f7b91b04 is the first bad commit
commit 1d82fc2e6824bf83159389729c31a942f7b91b04
Author: Jan Hubicka
Date: Tue Nov 21 15:17:16 2023 +0100
optimize std::vector::push_back
caused
FAIL: g++.dg/opt/pr110879.C -std=gnu++98 scan-tree-dump-not
On Linux/x86_64,
6bf66276e3e41d5d92f7b7260e98b6a111653805 is the first bad commit
commit 6bf66276e3e41d5d92f7b7260e98b6a111653805
Author: Richard Biener
Date: Wed Nov 22 11:10:41 2023 +0100
tree-optimization/112344 - wrong final value replacement
caused
FAIL:
On Linux/x86_64,
6e9ee44d96e5bda8808dd9d8ccf58d2525383f6b is the first bad commit
commit 6e9ee44d96e5bda8808dd9d8ccf58d2525383f6b
Author: Martin Uecker
Date: Thu Apr 13 19:35:15 2023 +0200
Reduce false positives for -Wnonnull for VLA parameters [PR98541]
caused
FAIL: gcc.dg/Wnonnull-4.c
On Linux/x86_64,
20a3c74c347429c109bc7002285b735be83f6a0b is the first bad commit
commit 20a3c74c347429c109bc7002285b735be83f6a0b
Author: Sebastian Huber
Date: Tue Nov 14 21:36:51 2023 +0100
gcov: Improve -fprofile-update=atomic
caused
FAIL: gcc.dg/tree-ssa/ssa-lim-11.c
On Linux/x86_64,
3cd3a09b3f91a1d023cb180763d40598d6bb274b is the first bad commit
commit 3cd3a09b3f91a1d023cb180763d40598d6bb274b
Author: Richard Sandiford
Date: Sat Nov 11 17:28:55 2023 +
mode-switching: Add note problem
caused
FAIL: ext/pb_ds/example/store_hash.cc -std=gnu++17
On Linux/x86_64,
41aacdea55c5d795a7aa195357d966645845d00e is the first bad commit
commit 41aacdea55c5d795a7aa195357d966645845d00e
Author: Sebastian Huber
Date: Mon Nov 20 15:26:38 2023 +0100
gcov: Fix integer types in gen_counter_update()
caused
FAIL: gcc.dg/tree-prof/time-profiler-3.c
On Linux/x86_64,
3f176e1adc6bc9cc2c21222d776b51d9f43cb66b is the first bad commit
commit 3f176e1adc6bc9cc2c21222d776b51d9f43cb66b
Author: Tamar Christina
Date: Thu Nov 9 13:59:39 2023 +
middle-end: optimize fneg (fabs (x)) to copysign (x, -1) [PR109154]
caused
FAIL:
On Linux/x86_64,
9251db0dabc8e75c31b49a5b589124e9a2bc8299 is the first bad commit
commit 9251db0dabc8e75c31b49a5b589124e9a2bc8299
Author: Hongyu Wang
Date: Thu Nov 9 13:11:41 2023 +0800
[i386] APX: Fix EGPR usage in several patterns.
caused
FAIL:
Pushed to r14-5863.
在 2023/11/18 下午2:59, Guo Jie 写道:
For the following immediate load operation in
gcc/testsuite/gcc.target/loongarch/imm-load1.c:
long long r = 0x0101010101010101;
Before this patch:
lu12i.w $r15,16842752>>12
ori $r15,$r15,257
Hi,
"Kewen.Lin" writes:
> Hi,
>
> on 2023/11/15 11:02, Jiufu Guo wrote:
>> Hi,
>>
>> For constants with 16bit values, 'li or lis' can be used to generate
>> the value. For 34bit constant, 'pli' is ok to generate the value.
>> For example: 0xULL, "pli 3,1717986918; rldimi
On 11/26/23 20:44, waffl3x wrote:
The other problem I'm having is
auto f0 = [n = 5, ](this auto const&){ n = 10; };
This errors just fine, the lambda is unconditionally const so
LAMBDA_EXPR_MUTABLE_P flag is set for the closure.
This on the other hand does not. The constness of the captures
> -Original Message-
> From: Gerald Pfeifer
> Sent: Saturday, November 25, 2023 7:29 PM
> To: Jiang, Haochen
> Cc: gcc-patches@gcc.gnu.org; Liu, Hongtao ;
> ubiz...@gmail.com
> Subject: Re: [PATCH] [gcc-wwwdocs]gcc-13/14: Mention Intel new ISA and march
> support
>
> On Mon, 17 Jul
> > > > OKAY, I figured out SOMETHING, I think this should be fine. As noted in
> > > > the comments, this might be a better way of handling the static lambda
> > > > case too. This is still a nasty hack so it should probably be done
> > > > differently, but I question if making a whole new fntype
> > Now with that out of the way, I do still kind of feel icky about it.
> > This really is a MASSIVE edge case that will almost never matter. As
> > far as I know, instantiating explicitly like so...
> >
> > auto f = [x = 42](this auto&&) -> int { return x; };
> > int (*fp)(int&) =
On 11/26/23 18:10, waffl3x wrote:
On Sunday, November 26th, 2023 at 2:30 PM, Jason Merrill
wrote:
On 11/24/23 20:14, waffl3x wrote:
OKAY, I figured out SOMETHING, I think this should be fine. As noted in
the comments, this might be a better way of handling the static lambda
case too. This
In a recent all-target test-round investigating XPASSes for
this file, I noticed this line XPASSing for MMIX. From the
commit history it's obvious it was left out from related
target-xfail tweaks, now the last target xfailing a bogus
warning for this line.
* gcc.dg/uninit-pred-9_b.c:
On Sunday, November 26th, 2023 at 2:30 PM, Jason Merrill
wrote:
>
>
> On 11/24/23 20:14, waffl3x wrote:
>
> > OKAY, I figured out SOMETHING, I think this should be fine. As noted in
> > the comments, this might be a better way of handling the static lambda
> > case too. This is still
Thanks Joseph, I will sent an updated series tomorrow.
Richard, maybe you could look at what I wrote below
about my use of TYPE_CANONICAL ? Does this make sense?
Am Donnerstag, dem 23.11.2023 um 23:47 + schrieb Joseph Myers:
> On Thu, 16 Nov 2023, Martin Uecker wrote:
>
> > Tell the
On 11/24/23 20:14, waffl3x wrote:
OKAY, I figured out SOMETHING, I think this should be fine. As noted in
the comments, this might be a better way of handling the static lambda
case too. This is still a nasty hack so it should probably be done
differently, but I question if making a whole new
On Nov 24, 2023, at 7:15 PM, Hans-Peter Nilsson wrote:
>
> While looking at the various targets, I found that the m32r
> target has two options implemented as opposites:
> -mbranch-cost=1 and -mbranch-cost=2, that have a bug that
> makes them yield their functionally opposite effect;
> i.e.
Hello,
Le 23/11/2023 à 22:59, Harald Anlauf a écrit :
Dear all,
the PR is about a redundant obsolescence warning for COMMON when
a symbols appears in the scope of a submodule. As we did not warn
for use-associated symbols, it seemed natural to extend this to
symbols that are used in a
Test on hppa64-hp-hpux11.11. Committed to trunk.
Dave
---
Skip analyzer strndup test on hppa*-*-hpux*
2023-11-26 John David Anglin
gcc/testsuite/ChangeLog:
* gcc.dg/analyzer/strndup-1.c: Skip on hppa*-*-hpux*.
diff --git a/gcc/testsuite/gcc.dg/analyzer/strndup-1.c
Tested on hppa64-hp-hpux11.11. Committed to trunk.
Dave
---
Skip analyzer socket tests on hppa*-*-hpux*
2023-11-26 John David Anglin
gcc/testsuite/ChangeLog:
* gcc.dg/analyzer/fd-glibc-datagram-client.c: Skip on hppa*-*-hpux*.
* gcc.dg/analyzer/fd-glibc-datagram-socket.c:
On 22 November 2023 23:23:41 CET, Jeff Law wrote:
>
>
>On 11/20/23 11:56, Dimitar Dimitrov wrote:
>> On Sun, Nov 19, 2023 at 05:47:56PM -0700, Jeff Law wrote:
>> ...
>>> + enum rtx_code xcode = GET_CODE (x);
>>> + if (xcode == SET)
>>> + {
>>> + const_rtx dst = SET_DEST (x);
>>>
Tested on hppa64-hp-hpux11.11. Committed to trunk.
Dave
---
hppa: Fix pr104869.C on hpux
2023-11-26 John David Anglin
gcc/testsuite/ChangeLog:
* g++.dg/pr104869.C: Add attribute visibility default to
main prototype.
diff --git a/gcc/testsuite/g++.dg/pr104869.C
Avoid using 'network sort' (a misnomer) in sort.cc, the correct term is
'sorting networks'.
gcc/ChangeLog:
* sort.cc: Use 'sorting networks' in comments.
---
gcc/sort.cc | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/gcc/sort.cc b/gcc/sort.cc
index
Tested on hppa64-hp-hpux11.11. Committed to trunk.
Dave
---
hppa: Really fix g++.dg/modules/bad-mapper-1.C on hpux
2023-11-26 John David Anglin
gcc/testsuite/ChangeLog:
* g++.dg/modules/bad-mapper-1.C: Add hppa*-*-hpux* to dg-error
"this-will-not-work" targets.
diff --git
Szabolcs Nagy writes:
> On aarch64 this caused ICE with pragma push_options since
>
> commit ae54c1b09963779c5c3914782324ff48af32e2f1
> Author: Wilco Dijkstra
> CommitDate: 2022-06-01 18:13:57 +0100
>
> AArch64: Cleanup option processing code
>
> The failure is at pop_options:
>
>
Szabolcs Nagy writes:
> gcc/testsuite/ChangeLog:
>
> * gcc.target/aarch64/eh_return-2.c: New test.
> * gcc.target/aarch64/eh_return-3.c: New test.
>
> ---
> v2: check-function-bodies in eh_return-3.c
> (this is not very robust, but easier to read)
> ---
>
> On 26 Nov 2023, at 14:24, Sebastian Huber
> wrote:
>
> On 26.11.23 11:15, Iain Sandoe wrote:
>>> On 26 Nov 2023, at 10:05, Sebastian
>>> Huber wrote:
>>>
>>> On 26.11.23 01:35, Iain Sandoe wrote:
> On 25 Nov 2023, at 21:44, Sebastian
> Huber wrote:
>
> On 25.11.23
On 26.11.23 11:15, Iain Sandoe wrote:
On 26 Nov 2023, at 10:05, Sebastian Huber
wrote:
On 26.11.23 01:35, Iain Sandoe wrote:
On 25 Nov 2023, at 21:44, Sebastian Huber
wrote:
On 25.11.23 14:59, Richard Biener wrote:
On Sat, Nov 25, 2023 at 12:26 PM Sebastian Huber
wrote:
Szabolcs Nagy writes:
> EH returns no longer rely on clobbering the return address on the stack
> so forcing a stack frame is not necessary.
>
> This does not actually change the code gen for the unwinder since there
> are calls before the EH return.
>
> gcc/ChangeLog:
>
> *
Szabolcs Nagy writes:
> The expected way to handle eh_return is to pass the stack adjustment
> offset and landing pad address via
>
> EH_RETURN_STACKADJ_RTX
> EH_RETURN_HANDLER_RTX
>
> to the epilogue that is shared between normal return paths and the
> eh_return paths. EH_RETURN_HANDLER_RTX
Hi Marek,
The new test at gcc.target/i386/cf_check-6.c fails on darwin with:
Excess errors:
cc1: warning: '-fhardened' not supported for this target
Other tests are only run on Linux, so I added this to
gcc.target/i386/cf_check-6.c as well.
Pushed as
Hi Uros,
The new test at gcc.target/i386/pr112686.c fails on darwin with:
Excess errors:
cc1: error: '-fsplit-stack' currently only supported on GNU/Linux
cc1: error: '-fsplit-stack' is not supported by this compiler configuration
It needs an /* { dg-require-effective-target split_stack } */
> On 26 Nov 2023, at 10:05, Sebastian Huber
> wrote:
>
> On 26.11.23 01:35, Iain Sandoe wrote:
>>> On 25 Nov 2023, at 21:44, Sebastian Huber
>>> wrote:
>>>
>>> On 25.11.23 14:59, Richard Biener wrote:
On Sat, Nov 25, 2023 at 12:26 PM Sebastian Huber
wrote:
>
On 26.11.23 01:35, Iain Sandoe wrote:
On 25 Nov 2023, at 21:44, Sebastian Huber
wrote:
On 25.11.23 14:59, Richard Biener wrote:
On Sat, Nov 25, 2023 at 12:26 PM Sebastian Huber
wrote:
contrib/ChangeLog
Did you verify an in-tree build with these works and the testsuite
is clean?
I
On Nov 26 2023, Gerald Pfeifer wrote:
> On Fri, 24 Nov 2023, Tobias Burnus wrote:
>> Comments before I commit it?
>
> + https://gcc.gnu.org/wiki/OpenACC;>OpenACC
> +OpenACC 2.7: The self clause was added to be used on
> + compute constructs and the default clause for data
> +
Re-check again RVV ISA, I find that we can't allow AVL propagation not only
for vrgather, but also slidedown instructions.
Committed.
PR target/112599
gcc/ChangeLog:
* config/riscv/riscv-avlprop.cc (avl_can_be_propagated_p): Add
slidedown.
(vlmax_ta_p): Ditto.
On Fri, 24 Nov 2023, Tobias Burnus wrote:
> Comments before I commit it?
+ https://gcc.gnu.org/wiki/OpenACC;>OpenACC
+OpenACC 2.7: The self clause was added to be used on
+ compute constructs and the default clause for data
+ constructs.
+
+
Where does that come from? I'm
59 matches
Mail list logo
