https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104866
--- Comment #4 from CVS Commits ---
The releases/gcc-11 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:502fd5575bfe0793ef4dc90dd714755e9878f308
commit r11-10497-g502fd5575bfe0793ef4dc90dd714755e9878f308
Author: Detlef
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104866
Jonathan Wakely changed:
What|Removed |Added
Known to fail||11.1.0
Known to work|11.2.1
This is PR 96088 but this time for _Rb_tree based containers.
I guess it won't go in for the moment but I wanted to submit it already
because of the changes I had to do in stl_functions.h. It sounds like
missing parts for C++11 move-semantic. I still need to run all tests to
see if they can
Here the ahead-of-time overload set pruning in finish_call_expr is
unintentionally returning a CALL_EXPR whose pruned callee is wrapped in
an ADDR_EXPR, despite the original callee not being wrapped in an
ADDR_EXPR. This ends up causing a bogus declaration matching error in
the below testcase
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108639
--- Comment #8 from Jakub Jelinek ---
(In reply to Aldy Hernandez from comment #5)
> (In reply to Jakub Jelinek from comment #3)
> > Created attachment 54391 [details]
> > gcc13-pr108639.patch
> >
> > Untested fix.
>
> I think the problem is
Tested x86_64-linux, built on avr. Pushed to trunk.
I might backport this to gcc-12 too, although realistically I doubt
anybody is going to try to use the filesystem library on avr anyway, so
it doesn't matter.
-- >8 --
Because avr-libc defines most error numbers with duplicate
values it's not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108641
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
Tested powerpc64le-linux. Pushed to trunk.
This could be backported to gcc-11 and gcc-12 but I have no immediate
plans to do that (it's needed on trunk because of the new stuff in
and that stuff isn't on the branches).
-- >8 --
Unlike the new str()&& members in , there is no real difficulty
in
The new __dmr type that is being added as a possible future PowerPC instruction
set bumps into a structure field size issue. The size of the __dmr type is
1024 bits.
The precision field in tree_type_common is currently 10 bits, so if you store
1,024 into field, you get a 0 back. When you get 0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107574
Marek Polacek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108639
--- Comment #7 from Aldy Hernandez ---
Jakub, take a look and see if you agree. I've fired off some tests.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108639
--- Comment #6 from Aldy Hernandez ---
Created attachment 54393
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54393=edit
untested patch for irange::operator==
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108639
Aldy Hernandez changed:
What|Removed |Added
CC||aldyh at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108500
--- Comment #17 from dhekir at gmail dot com ---
To be honest, the "real" test case is very similar to the last one I sent: it's
a semi-generated code, with some initialization of the data in the beginning,
and then a lot of statements which
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108636
Jonathan Wakely changed:
What|Removed |Added
Summary|C++20 undefined reference |[10/11/12 Regression] C++20
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108642
--- Comment #5 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #3)
> Which of course is not documented ...
They are documented but not in a decent way:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108642
--- Comment #4 from David Spickett ---
Of course, I was just looking at at assembly output in compiler explorer and
then locally I didn't link the object. That's why it seemed to work.
Compiling and linking I get:
$
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108642
--- Comment #3 from Andrew Pinski ---
GCC has a builtin already for getting fpsr already too:
__builtin_aarch64_get_fpsr
Which of course is not documented ...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108642
--- Comment #2 from Andrew Pinski ---
Note the ACLE does not require "fpsr" to be supported either only
"o0:op1:CRn:CRm:op2" format is listed there ...
On Thu, Feb 02, 2023 at 02:31:53PM +, Qing Zhao wrote:
>
> > On Feb 2, 2023, at 3:33 AM, Richard Biener wrote:
> >
> > On Wed, 1 Feb 2023, Siddhesh Poyarekar wrote:
> >
> >> On 2023-02-01 13:24, Qing Zhao wrote:
> >>>
> >>>
> On Feb 1, 2023, at 11:55 AM, Siddhesh Poyarekar
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108642
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-02-02
Target|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108643
Bug ID: 108643
Summary: Initializing parameter by ref in coroutine function
causes memory corruption
Product: gcc
Version: 12.2.1
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108642
Bug ID: 108642
Summary: ACLE function __arm_wsr missing when compiling in C++
mode for AArch64
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity:
Tested powerpc64le-linux. Pushed to trunk.
The source code changes should be backported (the linker script changes
aren't needed because those symbols aren't present on the branches).
-- >8 --
With -fkeep-inline-functions there are linker errors when including
. This happens because there are
Tested powerpc64le-linux. Pushed to trunk.
-- >8 --
This was approved at the October 2021 plenary.
libstdc++-v3/ChangeLog:
* include/std/variant (variant::operator=): Implement resolution
of LWG 3585.
* testsuite/20_util/variant/lwg3585.cc: New test.
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108636
--- Comment #3 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:db8d6fc572ec316ccfcf70b1dffe3be0b1b37212
commit r13-5662-gdb8d6fc572ec316ccfcf70b1dffe3be0b1b37212
Author: Jonathan Wakely
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60512
Jason Merrill changed:
What|Removed |Added
Resolution|WORKSFORME |---
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108384
--- Comment #13 from Martin Jambor ---
I have proposed a fix on the mailing list:
https://gcc.gnu.org/pipermail/gcc-patches/2023-February/611194.html
Hi,
when the compiled program contains type mismatches between callers and
callees when it comes to a parameter, IPA-CP can try to propagate one
constant from callers while IPA-SRA may try to split a parameter
expecting a value of a different size on the same offset. This then
currently leads to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106170
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107897
Jakub Jelinek changed:
What|Removed |Added
CC||jason at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104647
Andrew Pinski changed:
What|Removed |Added
Target Milestone|10.5|13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108638
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |DUPLICATE
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108639
Jakub Jelinek changed:
What|Removed |Added
CC||dcb314 at hotmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104647
Marek Polacek changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108639
Jakub Jelinek changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108641
Bug ID: 108641
Summary: Hooking MS-MPI system into the NONMEM installation
failed
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: normal
On 02/02/2023 14:59, Tobias Burnus wrote:
Maybe it becomes better reviewable with an attached patch ...
On 02.02.23 15:31, Tobias Burnus wrote:
Now that the stack handling has been changed for AMDGCN, this patch
enables reverse offload.
(cf. today's "[committed] amdgcn, libgomp: Manually
Prathamesh Kulkarni writes:
>> >> > I have attached a patch that extends the transform if one half is dup
>> >> > and other is set of constants.
>> >> > For eg:
>> >> > int8x16_t f(int8_t x)
>> >> > {
>> >> > return (int8x16_t) { x, 1, x, 2, x, 3, x, 4, x, 5, x, 6, x, 7, x, 8 };
>> >> > }
>> >>
> > Thank you so much. Kito helped me fix it already.
> > RVV instruction patterns can have CSE optimizations now.
> What was the issue?
VL and VTYPE isn't listed in fixed register so CSE feel that isn't
cheap (See CHEAP_REGNO in cse.cc),
but actually it's kind of mistake sett for VL and VTYPE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108639
Jakub Jelinek changed:
What|Removed |Added
CC||amacleod at redhat dot com
--- Comment
Maybe it becomes better reviewable with an attached patch ...
On 02.02.23 15:31, Tobias Burnus wrote:
Now that the stack handling has been changed for AMDGCN, this patch
enables reverse offload.
(cf. today's "[committed] amdgcn, libgomp: Manually allocated stacks"
patch email/commit
by Andrew).
insn_info tried to save space by storing the number of
definitions in a 16-bit bitfield. The justification was:
// ... FIRST_PSEUDO_REGISTER + 1
// is the maximum number of accesses to hard registers and memory, and
// MAX_RECOG_OPERANDS is the maximum number of pseudos that can be
//
This test was failing on aarch64 because aarch64 overrides
TARGET_CASE_VALUES_THRESHOLD. The maximum value that allows
the test to pass appears to be 6, but the default threshold
is 4 or 5 (depending on whether casesi is provided).
Going for 4 seemed safest, in case any target-specific
features
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108086
--- Comment #17 from CVS Commits ---
The trunk branch has been updated by Richard Sandiford :
https://gcc.gnu.org/g:cd41085a37b8288dbdfe0f81027ce04b978578f1
commit r13-5658-gcd41085a37b8288dbdfe0f81027ce04b978578f1
Author: Richard Sandiford
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108508
--- Comment #4 from CVS Commits ---
The trunk branch has been updated by Richard Sandiford :
https://gcc.gnu.org/g:f4e1b46618ef3bd7933992ab79f663ab9112bb80
commit r13-5657-gf4e1b46618ef3bd7933992ab79f663ab9112bb80
Author: Richard Sandiford
On Wed, 1 Feb 2023 at 21:56, Richard Sandiford
wrote:
>
> Prathamesh Kulkarni writes:
> > On Thu, 12 Jan 2023 at 21:21, Richard Sandiford
> > wrote:
> >>
> >> Prathamesh Kulkarni writes:
> >> > On Tue, 6 Dec 2022 at 07:01, Prathamesh Kulkarni
> >> > wrote:
> >> >>
> >> >> On Mon, 5 Dec 2022
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108640
Bug ID: 108640
Summary: ICE compiling busybox for m68k in change_address_1, at
emit-rtl.cc:2283
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity:
We set VL/VTYPE these 2 implicit global status denpency register as fixed reg.
Then CSE can do the optimization now.
>> Yea. I'm wondering about when the right place to introduce these
>>dependencies might be. I'm still a few months out from worrying about
>>RVV, but it's not too far away.
You
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108639
Jakub Jelinek changed:
What|Removed |Added
Version|unknown |13.0
Ever confirmed|0
> On Feb 2, 2023, at 8:54 AM, Richard Biener wrote:
>
> On Thu, 2 Feb 2023, Qing Zhao wrote:
>
>>
>>
>>> On Feb 2, 2023, at 3:07 AM, Richard Biener wrote:
>>>
>>> On Wed, 1 Feb 2023, Qing Zhao wrote:
>>>
> On Feb 1, 2023, at 6:41 AM, Richard Biener wrote:
>
>
On 2/2/23 05:35, juzhe.zh...@rivai.ai wrote:
Thank you so much. Kito helped me fix it already.
RVV instruction patterns can have CSE optimizations now.
What was the issue?
jeff
On 2/2/23 05:26, Richard Biener wrote:
On Thu, 2 Feb 2023, juzhe.zh...@rivai.ai wrote:
Yeah, Thanks. You are right. CSE should do the job.
Now I know the reason CSE failed to optimize is I include
VL_REGNUM(66)/VTYPE_RENUM(67) hard reg
as the dependency of pred_broadcast:
(insn 19 18 20 4
> On Feb 2, 2023, at 3:33 AM, Richard Biener wrote:
>
> On Wed, 1 Feb 2023, Siddhesh Poyarekar wrote:
>
>> On 2023-02-01 13:24, Qing Zhao wrote:
>>>
>>>
On Feb 1, 2023, at 11:55 AM, Siddhesh Poyarekar
wrote:
On 2023-01-31 09:11, Qing Zhao wrote:
> Update
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108626
--- Comment #8 from Marat Radchenko ---
Also, quote from C17 standard:
Like string literals, const-qualified compound literals can be placed into
read-only memory and *can even be shared*. (6.5.2.5 p 13).
Now that the stack handling has been changed for AMDGCN, this patch enables
reverse offload.
(cf. today's "[committed] amdgcn, libgomp: Manually allocated stacks" patch
email/commit
by Andrew).
Any comments, suggestions?
Tobias
-
Siemens Electronic Design Automation GmbH;
Hi!
The recent change to undo the tree_code_type/tree_code_length
excessive duplication apparently broke building the Linux kernel
plugin. While it is certainly desirable that GCC plugins are built
with the same compiler as GCC has been built and with the same options
(at least the important
/gcc-trunk
--enable-sanitizers --enable-languages=c,c++ --disable-werror --enable-multilib
--with-system-zlib
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 13.0.1 20230202 (experimental) [master r13-5642-g66d700af5bb] (GCC)
[539] %
[539] % gcctk -O1 small.c
small.c
Hi all,
A reminder that the next open meeting to discuss on the RISC-V V C Intrinsic
API v1.0 release is going to
be held later on 2022/02/02 6AM (GMT -7) / 11PM (GMT +8).
The agenda can be found in the second page of the meeting slides (link
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108633
David Malcolm changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Integration testing shows it fixes a false positive seen on qemu, and
has no other changes.
Pushed to trunk as r13-5655-gd84dc419e692d4.
gcc/analyzer/ChangeLog:
PR analyzer/108633
* sm-fd.cc
Successfully regrtested on x86_64-pc-linux-gnu.
Pushed to trunk as r13-5654-g598e10cf415f0a.
gcc/testsuite/ChangeLog:
* gcc.dg/analyzer/deref-before-check-qemu-qtest_rsp_args.c: New test.
Signed-off-by: David Malcolm
---
.../deref-before-check-qemu-qtest_rsp_args.c | 73
Found when testing AMD GCN offloading, the second issue came up with
libgomp.fortran/reverse-offload-5.f90. (But oddly not with nvptx.)
While the first one (new test: libgomp.fortran/reverse-offload-6.f90)
came up when debugging the issue.
Tobias
-
Siemens Electronic Design
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108633
--- Comment #1 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:d84dc419e692d42c3b1e0c82e972c8a6f4c71389
commit r13-5655-gd84dc419e692d42c3b1e0c82e972c8a6f4c71389
Author: David Malcolm
Date:
On Wed, Jan 25, 2023 at 16:06:31 -0500, Ben Boeckel wrote:
> This patch series adds initial support for ISO C++'s [P1689R5][], a
> format for describing C++ module requirements and provisions based on
> the source code. This is required because compiling C++ with modules is
> not embarrassingly
On Wed, Jan 25, 2023 at 16:06:31 -0500, Ben Boeckel wrote:
> This patch series adds initial support for ISO C++'s [P1689R5][], a
> format for describing C++ module requirements and provisions based on
> the source code. This is required because compiling C++ with modules is
> not embarrassingly
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108500
--- Comment #16 from Richard Biener ---
(In reply to Richard Biener from comment #14)
> Martin, can you look at the SRA issue? Do you want me to create a separate
> bugreport for this? The IL into SRA looks like
>
>:
> s2D.2755 = {};
>
On Thu, 2 Feb 2023, Qing Zhao wrote:
>
>
> > On Feb 2, 2023, at 3:07 AM, Richard Biener wrote:
> >
> > On Wed, 1 Feb 2023, Qing Zhao wrote:
> >
> >>
> >>
> >>> On Feb 1, 2023, at 6:41 AM, Richard Biener wrote:
> >>>
> >>> On Tue, 31 Jan 2023, Qing Zhao wrote:
> >>>
> GCC extension
> On Feb 2, 2023, at 3:07 AM, Richard Biener wrote:
>
> On Wed, 1 Feb 2023, Qing Zhao wrote:
>
>>
>>
>>> On Feb 1, 2023, at 6:41 AM, Richard Biener wrote:
>>>
>>> On Tue, 31 Jan 2023, Qing Zhao wrote:
>>>
GCC extension accepts the case when a struct with a flexible array member
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108636
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #2 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108638
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |13.0
Component|c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108638
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
ack, just let you know reviewing this patch is on my todo list :)
My first impression is...you need to write something in your
changelog, it seems like generated by contrib/git-commit-mklog.py
without any modification.
On Thu, Feb 2, 2023 at 1:46 PM Jin Ma wrote:
>
> This patch adds the 'Zfa'
On Thu, Feb 2, 2023 at 12:41 PM Iain Sandoe wrote:
>
>
>
> > On 30 Jan 2023, at 07:48, Richard Biener wrote:
> >
> > On Sun, Jan 29, 2023 at 12:35 PM Iain Sandoe via Gcc-patches
> > wrote:
> >>
> >> Technically, this is seems to be a regression somewhere between 4.2 and
> >> 4.6 but, it seems,
Good catch! thanks for fixing that, committed to trunk :)
On Thu, Feb 2, 2023 at 7:46 PM Jin Ma wrote:
>
> MAX_MATCH_SCORE is not assigned anywhere except initialized to 0,
> causing BEST_MATCH_MULTI_LIB to always be 0 or -1, which will
> cause the result of TARGET_COMPUTE_MULTILIB hook to fail.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108636
--- Comment #1 from Jonathan Wakely ---
Trunk has some additional errors:
/usr/bin/ld: /tmp/ccXeUWH9.o: in function
`std::filesystem::__cxx11::directory_iterator::operator==(std::default_sentinel_t)
const':
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108626
--- Comment #7 from Marat Radchenko ---
While playing with it more, I found that clang behaves in a very strange way.
While they do combine `const char* const` + `const char[]`, the DO NOT combine
two `const char[]` together. I don't have any
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108638
Bug ID: 108638
Summary: Another ice in decompose, at wide-int.h:984
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Hello Flint,
On Sat, Jan 28 2023, hmsjwzb via Gcc wrote:
> Hi GCC developers,
>
> I am learning GCC. But the GCC code is hard to understand.
We are delighted you found looking into GCC interesting. I definitely
agree that GCC source can be hard to read, especially for newcomers but
often
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108484
--- Comment #7 from Sam James ---
Could you add 108463 to See Also? Thanks.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108484
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106746
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108463
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107300
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60160
--- Comment #9 from Andre Heider ---
See also https://github.com/rui314/mold/issues/977
mold v1.10.1 can't handle crt files which are built with LTO enabled.
But it sounds more like LTO on crt as-is produces the wrong thing?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108463
--- Comment #16 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:465a9c51e7d5bafa7a81195b5af20f2a54f22210
commit r13-5652-g465a9c51e7d5bafa7a81195b5af20f2a54f22210
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106746
--- Comment #27 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:465a9c51e7d5bafa7a81195b5af20f2a54f22210
commit r13-5652-g465a9c51e7d5bafa7a81195b5af20f2a54f22210
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108484
--- Comment #5 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:465a9c51e7d5bafa7a81195b5af20f2a54f22210
commit r13-5652-g465a9c51e7d5bafa7a81195b5af20f2a54f22210
Author: Jakub Jelinek
Date:
On Thu, Feb 02, 2023 at 12:19:56PM +0100, Tobias Burnus wrote:
> There is less new in TR11 as claimed ... 'strict' on grainsize/num_tasks is
> already
> in OpenMP 5.1, it is implemented and also listed as 'Y' under 5.1.
> Only 'num_threads(strict: int-expr)' is new in TR11.
>
> Tobias
>
Thank you so much. Kito helped me fix it already.
RVV instruction patterns can have CSE optimizations now.
juzhe.zh...@rivai.ai
From: Richard Biener
Date: 2023-02-02 20:26
To: juzhe.zh...@rivai.ai
CC: gcc-patches; kito.cheng; richard.sandiford; jeffreyalaw; apinski
Subject: Re: Re: [PATCH]
On Thu, Feb 2, 2023 at 10:49 AM Richard Sandiford via Gcc-patches
wrote:
>
> Since rtl-ssa isn't a real/native SSA representation, it has
> to honour the constraints of the underlying rtl representation.
> Part of this involves maintaining an rpo list of definitions
> for each rtl register,
On Thu, 2 Feb 2023, juzhe.zh...@rivai.ai wrote:
> Yeah, Thanks. You are right. CSE should do the job.
> Now I know the reason CSE failed to optimize is I include
> VL_REGNUM(66)/VTYPE_RENUM(67) hard reg
> as the dependency of pred_broadcast:
> (insn 19 18 20 4 (set (reg:VNx1DI 152)
> >
On Wed, Feb 1, 2023 at 7:12 PM Andrew MacLeod via Gcc-patches
wrote:
>
> We can reset SCEV after we fold, then SCEVs cache shouldn't have
> anything in it when we go to remove ssa-names in remove_unreachable().
>
> We were resetting it later sometimes if we were processing the array
> bounds
Ping!!
From: Gcc-patches
on behalf of
Srinath Parvathaneni via Gcc-patches
Sent: 27 January 2023 17:44
To: gcc-patches@gcc.gnu.org
Cc: nd ; Richard Earnshaw ; Kyrylo
Tkachov
Subject: [PATCH][GCC] arm: Optimize arm-mlib.h header inclusion (pr108505).
Hello,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108625
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
Summary|[11/12/13
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108625
--- Comment #3 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:605d1297b91c2c7c23ccfe669e66dda5791d1f55
commit r13-5651-g605d1297b91c2c7c23ccfe669e66dda5791d1f55
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108636
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108637
Bug ID: 108637
Summary: ASAN at -O2 misses a stack-use-after-scope
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108636
Bug ID: 108636
Summary: C++20 to undefined reference to
`std::filesystem::__cxx11::path::_List::type(std::file
system::__cxx11::path::_Type)' with
On Thu, 2 Feb 2023, Alexandre Oliva wrote:
> On Jan 27, 2023, Jakub Jelinek wrote:
>
> > Now, 1) is precondition of 2), we can only subst the VALUEs if we
> > have actually looked the address up, but as can be seen on that testcase,
> > we are relying on at least the 1) to be done because we
101 - 200 of 247 matches
Mail list logo
