On Wed, Aug 3, 2022 at 4:41 PM Kong, Lingling via Gcc-patches
wrote:
>
> Hi,
>
> Old patch has some mistake in `*movbf_internal` , now disable BFmode constant
> double move in `*movbf_internal`.
LGTM.
>
> Thanks,
> Lingling
>
> > -Original Message-
> > From: Kong, Lingling
> > Sent:
For neg, the patch create a vec_init as [ a, -a, a, -a, ... ] and no
vec_step is needed to update vectorized iv since vf is always multiple
of 2(negative * negative is positive).
For shift, the patch create a vec_init as [ a, a >> c, a >> 2*c, ..]
as vec_step as [ c * nunits, c * nunits, c *
On Linux/x86_64,
9bb19e143cfe8863e2e79d4176b5d7e997b08c5f is the first bad commit
commit 9bb19e143cfe8863e2e79d4176b5d7e997b08c5f
Author: Tamar Christina
Date: Wed Aug 3 16:00:39 2022 +0100
middle-end: Support recognition of three-way max/min.
caused
FAIL: gcc.dg/analyzer/pr96653.c
Hi Segher,
On 4/8/2022 上午 12:54, Segher Boessenkool wrote:
> Hrm. But the maddld insn is useful for SImode as well, in 32-bit mode,
> it is just its name that is a bit confusing then. Sorry for confusing
> things :-(
>
> Add a test for SImode maddld as well?
Thanks for your comments.
Just
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106502
Eric Gallager changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43301
Eric Gallager changed:
What|Removed |Added
CC||aoliva at gcc dot gnu.org
--- Comment
One more ping for this patch
https://gcc.gnu.org/pipermail/gcc-patches/2022-June/596065.html
CC Jason since this changes discriminators emitted in dwarf.
Thanks,
Eugene
-Original Message-
From: Eugene Rozenfeld
Sent: Monday, June 27, 2022 12:45 PM
To: gcc-patches@gcc.gnu.org; Andi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106519
Tamar Christina changed:
What|Removed |Added
CC||tnfchris at gcc dot gnu.org
-bootstrap
--enable-checking=yes --prefix=/local/suz-local/software/local/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.0 20220803 (experimental) [maste
On 8/3/2022 2:44 PM, Prathamesh Kulkarni via Gcc-patches wrote:
On Thu, 4 Aug 2022 at 00:41, Sam Feifer via Gcc-patches
wrote:
This patch adds a new optimization to match.pd. The pattern, -x & 1,
now gets simplified to x & 1, reducing the number of instructions
produced.
Hi Sam,
No
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106520
Bug ID: 106520
Summary: 2+ index expressions in build_op_subscript are
incorrectly interpreted as comma expression
Product: gcc
Version: 12.1.0
Status: UNCONFIRMED
Note, I tried to send this out before, but it didn't seem to go out. Sorry if
you got it twice.
Sorry for the scatter shot mail that covers C++, Objective C++, Glibc,
etc. developers, but I wanted to discuss and get buy-in on changes to the
PowerPC GCC compiler that I would like to do in the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106519
seurer at gcc dot gnu.org changed:
What|Removed |Added
CC||seurer at gcc dot gnu.org
On Thu, 4 Aug 2022 at 00:41, Sam Feifer via Gcc-patches
wrote:
>
> This patch adds a new optimization to match.pd. The pattern, -x & 1,
> now gets simplified to x & 1, reducing the number of instructions
> produced.
Hi Sam,
No comments on patch, but wondering if we can similarly add another
On Wed, Aug 3, 2022 at 1:26 AM Richard Biener via Gcc-patches
wrote:
>
> On Wed, 3 Aug 2022, Tamar Christina wrote:
>
> >
> > > -Original Message-
> > > From: Richard Biener
> > > Sent: Tuesday, August 2, 2022 10:11 AM
> > > To: Tamar Christina
> > > Cc: Richard Biener ;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106519
Bug ID: 106519
Summary: [13 Regression] internal compiler error: in
gimple_phi_arg, at gimple.h:4594 by r13-1950
Product: gcc
Version: 13.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106518
Bug ID: 106518
Summary: Exchange/swap aware register allocation (generate xchg
in reload)
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity:
Hi Mike,
On Mon, Jul 25, 2022 at 04:15:05PM -0400, Michael Meissner wrote:
> Testing has shown that using the load vector pair and store vector pair
> instructions for block moves has some performance issues on power10.
> This patch eliminates the code setting -mblock-ops-vector-pair. If you
>
The path oracles killing_def () routine was removing an ssa-name from
each equivalence in the set. This was busy work that did not need to be
done.
when checking for an equivalence between A and B, the path oracle
requires that A be in B's set and B be in A's set. By setting the
This patch adds a new optimization to match.pd. The pattern, -x & 1,
now gets simplified to x & 1, reducing the number of instructions
produced.
This patch also adds tests for the optimization rule.
Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?
PR tree-optimization/106243
Never mind, just found how to do this:
/* { dg-warning "'-fstrict-flex-arrays' is not supported with a ISO C before
C99, ignored" "" { target *-*-* } 0 } */
And worked.
thanks.
Qing
> On Aug 3, 2022, at 2:52 PM, Qing Zhao via Gcc-patches
> wrote:
>
> Hi,
>
> My private cc1 issued the
Hi,
My private cc1 issued the following warning:
[opc@qinzhao-ol8u3-x86 gcc]$ sh t
cc1: warning: ‘-fstrict-flex-arrays’ is not supported with a ISO C before C99,
ignored
I’d like to add a testing case for this warning into gcc.dg directory, however,
I cannot find a proper
testing directive
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99888
--- Comment #3 from Segher Boessenkool ---
Your second option isn't correct: all these nops should be consecutive. Your
option 1 is fine :-)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25521
--- Comment #9 from Jose E. Marchesi ---
So I got feedback from the clang/llvm folks on this.
As you can see in [1] they asked the WG14 reflectors about the footnote 135 in
the C18 spec and their conclusion is that there is no normative
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106069
--- Comment #28 from Segher Boessenkool ---
(In reply to rsand...@gcc.gnu.org from comment #25)
> - On big-endian targets, vector loads and stores are assumed to put the
> first memory element at the most significant end of the vector
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106069
--- Comment #27 from Segher Boessenkool ---
IMO what vec_select calls element 0 is always in the first argument of the
vec_concat it works on, in BE as well as LE. But yes this is quite
underdefined
in our documentation, and who know what is
Ping patches.
Patch #1 of 5.
| Date: Thu, 28 Jul 2022 00:47:13 -0400
| Subject: [PATCH 1/5] IEEE 128-bit built-in overload support.
| Message-ID:
Patch #2 of 5.
| Date: Thu, 28 Jul 2022 00:48:51 -0400
| Subject: [PATCH 2/5] Support IEEE 128-bit overload round_to_odd built-in
functions.
|
Ping patch.
| Date: Mon, 25 Jul 2022 16:15:05 -0400
| Subject: [PATCH, V2] Do not enable -mblock-ops-vector-pair.
| Message-ID:
--
Michael Meissner, IBM
PO Box 98, Ayer, Massachusetts, USA, 01432
email: meiss...@linux.ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106517
Bug ID: 106517
Summary: RISC-V: Inefficient Generated Code for Floating Point
to Integer Rounds
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105090
Richard Earnshaw changed:
What|Removed |Added
Target Milestone|--- |13.0
On Tue, Aug 2, 2022 at 4:34 PM Jeff Law wrote:
>
>
>
> On 8/2/2022 11:43 AM, H.J. Lu wrote:
> > On Sat, Jul 30, 2022 at 1:30 PM Jeff Law via Gcc-patches
> > wrote:
> >>
> >>
> >> On 7/14/2022 3:55 PM, H.J. Lu via Gcc-patches wrote:
> >>> Check stack canary for noreturn function to catch stack
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105090
Richard Earnshaw changed:
What|Removed |Added
CC||andij.cr at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91674
Richard Earnshaw changed:
What|Removed |Added
Resolution|--- |DUPLICATE
On 8/3/2022 1:52 AM, Richard Sandiford via Gcc-patches wrote:
Takayuki 'January June' Suwa via Gcc-patches writes:
Emitting "(clobber (reg X))" before "(set (subreg (reg X)) (...))" keeps
data flow consistent, but it also increases register allocation pressure
and thus often creates many
Hi!
On Wed, Aug 03, 2022 at 04:24:15PM +0800, HAO CHEN GUI wrote:
> This patch changes the definition of TARGET_MADDLD and includes
> TARGET_POWERPC64, since maddld is a 64 bit instruction.
Hrm. But the maddld insn is useful for SImode as well, in 32-bit mode,
it is just its name that is a
The regexps in hte test btf-int-1.c were not working properly with the
commenting style of at least one target: powerpc64le-linux-gnu. This
patch changes the test to use better regexps.
Tested in bpf-unkonwn-none, x86_64-linux-gnu and powerpc64le-linux-gnu.
Pushed to master as obvious.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106515
--- Comment #4 from CVS Commits ---
The master branch has been updated by Jose E. Marchesi :
https://gcc.gnu.org/g:f0688c82ba8206a3d8960eb1d4821dc6a5f2a9f4
commit r13-1951-gf0688c82ba8206a3d8960eb1d4821dc6a5f2a9f4
Author: Jose E. Marchesi
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:Europe/London
X-LIC-LOCATION:Europe/London
BEGIN:DAYLIGHT
TZOFFSETFROM:+
TZOFFSETTO:+0100
TZNAME:BST
DTSTART:19700329T01
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106514
--- Comment #1 from Andrew Macleod ---
(In reply to Richard Biener from comment #0)
>
> Part of the sub-optimality is probably the equiv chain becoming very long
> (can we simply limit that?) and clearing bits in all the very many
> bitmaps
I have this program:
#include
template
T add (T x, T y) {
if (x > y)
return x + y;
else
return x;
}
template
T sub (T x, T y) {
if (x > y)
return x - y;
else
return x;
}
int main() {
int i1 = 10;
int i2 = 12;
double d1 = 10.0;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104992
seurer at gcc dot gnu.org changed:
What|Removed |Added
CC||seurer at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106516
seurer at gcc dot gnu.org changed:
What|Removed |Added
CC||bergner at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106516
Bug ID: 106516
Summary: New test case gcc.dg/pr104992.c fails
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
Martin Jambor writes:
> Hi Richard,
>
> On Fri, Nov 13 2020, Richard Sandiford via Gcc-patches wrote:
>> A later patch wants to be able to pass around subarray views of an
>> existing array. The standard class to do that is std::span, but it's
>> a C++20 thing. This patch just adds a cut-down
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106515
--- Comment #3 from Jose E. Marchesi ---
This is due to having not so good regular expressions in the test btf-int-1.c
and to a slightly different way than the powerpc backend has to comment lines
in assembly.
Working on a fix.
> -Original Message-
> From: Richard Biener
> Sent: Tuesday, June 21, 2022 8:43 AM
> To: Tamar Christina
> Cc: Richard Sandiford ; Richard Biener via Gcc-
> patches ; Richard Guenther
> ; nd
> Subject: Re: [PATCH 1/2]middle-end: Simplify subtract where both
> arguments are being bitwise
Hi Richard,
On Fri, Nov 13 2020, Richard Sandiford via Gcc-patches wrote:
> A later patch wants to be able to pass around subarray views of an
> existing array. The standard class to do that is std::span, but it's
> a C++20 thing. This patch just adds a cut-down version of it.
thanks a lot for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106515
--- Comment #2 from Jose E. Marchesi ---
Don't bother I just reproduced the issue in powerpc64le-linux-gnu.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106515
Jose E. Marchesi changed:
What|Removed |Added
CC||jose.marchesi at oracle dot com
---
I am pleased to announce that the GCC Steering Committee has appointed
Eugene Rozenfeld as AutoFDO maintainer.
Please join me in congratulating Eugene on his new role.
Eugene, please update your listing in the MAINTAINERS file.
Happy hacking!
David
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106515
Bug ID: 106515
Summary: [13 regression] gcc.dg/debug/btf/btf-int-1.c fails
after r13-1937-g5df04a7aa837a1
Product: gcc
Version: 13.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106514
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |12.2
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106514
Bug ID: 106514
Summary: [12/13 Regression] ranger slowness in path query
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105957
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104443
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|13.0|12.2
--- Comment #7 from Jonathan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105995
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|13.0|12.2
--- Comment #8 from Jonathan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105844
--- Comment #10 from Jonathan Wakely ---
Backported for 12.2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106248
--- Comment #11 from Jonathan Wakely ---
Backported for 12.2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106248
--- Comment #10 from CVS Commits ---
The releases/gcc-12 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:7a0ed28d4feb450f1ede5b52b57793a5df5b19fe
commit r12-8659-g7a0ed28d4feb450f1ede5b52b57793a5df5b19fe
Author: Jonathan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104443
--- Comment #6 from CVS Commits ---
The releases/gcc-12 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:1a9681e60964c7f7ce0892e14745e6dcf6100157
commit r12-8660-g1a9681e60964c7f7ce0892e14745e6dcf6100157
Author: Jonathan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105995
--- Comment #7 from CVS Commits ---
The releases/gcc-12 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:e562236851e06091256593aa0d3fbda60a28e45b
commit r12-8657-ge562236851e06091256593aa0d3fbda60a28e45b
Author: Jonathan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105957
--- Comment #4 from CVS Commits ---
The releases/gcc-12 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:2ef2de76dae5cac14e0de77ca7205e43be03ab22
commit r12-8655-g2ef2de76dae5cac14e0de77ca7205e43be03ab22
Author: Jonathan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92978
--- Comment #9 from CVS Commits ---
The releases/gcc-12 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:8a57deb926cd660c2eae7ed621d61a301ae0d523
commit r12-8654-g8a57deb926cd660c2eae7ed621d61a301ae0d523
Author: Jonathan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105844
--- Comment #9 from CVS Commits ---
The releases/gcc-12 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:8a57deb926cd660c2eae7ed621d61a301ae0d523
commit r12-8654-g8a57deb926cd660c2eae7ed621d61a301ae0d523
Author: Jonathan
On 8/3/22 12:20, Ilya Leoshkevich wrote:
> Bootstrapped and regtested on s390x-redhat-linux. Ok for master?
>
>
>
> dg.exp=pr104612.c fails with an ICE on s390x, because copysignv2sf3
> produces an insn that vsel is supposed to recognize, but can't,
> because it's not defined for V2SF. Fix by
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98421
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|11.3|10.5
--- Comment #5 from Jonathan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100748
--- Comment #13 from Jonathan Wakely ---
Fixed for 11.3 and 10.5 too.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103133
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|11.3|10.5
--- Comment #12 from Jonathan
Hello,
I've proposed a patch [1] for condition coverage profiling in gcc,
implemented in the middle-end alongside the branch coverage. I've
written most of the tests for C and a few for C++ and finally got around
to try it with a toy example for D and go and noticed something odd
about
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106513
--- Comment #2 from Krister Walfridsson ---
(In reply to Andreas Schwab from comment #1)
> This subexpression has undefined behaviour: (((int64_t) 0xff) << 56).
I thought that was allowed in GCC as the manual says
Hi Jakub,
This patch was reduced a bit and most of your comments were considered in the
last submission of the environment variable syntax extension patch
(https://gcc.gnu.org/pipermail/gcc-patches/2022-August/599175.html). This patch
also builds on that envvar patch version.
The nteams-var
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322
--- Comment #14 from Mathieu Malaterre ---
I can make the symptom go away with a single function attribute:
```
% diff -u *
--- /tmp/ii/mul_test.cc.ii.bad 2022-08-03 12:29:41.192263306 +
+++ /tmp/ii/mul_test.cc.ii.good 2022-08-03
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322
--- Comment #13 from Mathieu Malaterre ---
Created attachment 53407
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53407=edit
main function with no-tree-optimize attribute
Tested x86_64-linux, pushed to gcc-10 branch.
-- >8 --
The current std::list::merge code calls size() before starting to merge
any elements, so that the _M_size members can be updated after the merge
finishes. The work is done in a try-block so that the sizes can still be
updated in an exception
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322
--- Comment #12 from Mathieu Malaterre ---
Created attachment 53406
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53406=edit
main function with no-tree-optimize attribute
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98421
--- Comment #4 from CVS Commits ---
The releases/gcc-10 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:de802e4736613a585dcfd508acf73033f18aa4da
commit r10-10932-gde802e4736613a585dcfd508acf73033f18aa4da
Author: Jonathan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100748
--- Comment #12 from CVS Commits ---
The releases/gcc-10 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:18eecb8c4a97716d4bc4890b05c91f172fadc7b3
commit r10-10928-g18eecb8c4a97716d4bc4890b05c91f172fadc7b3
Author: Jonathan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103133
--- Comment #11 from CVS Commits ---
The releases/gcc-10 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:18eecb8c4a97716d4bc4890b05c91f172fadc7b3
commit r10-10928-g18eecb8c4a97716d4bc4890b05c91f172fadc7b3
Author: Jonathan
This patch to the middle-end's RTL expansion reorders the code in
emit_store_flag_1 so that the backend has more control over how best
to expand/split double word equality/inequality comparisons against
zero or minus one. With the current implementation, the middle-end
always decides to lower
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106513
--- Comment #1 from Andreas Schwab ---
This subexpression has undefined behaviour: (((int64_t) 0xff) << 56).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106513
Bug ID: 106513
Summary: bswap is incorrectly generated
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
On Tue, Aug 2, 2022 at 11:33 PM Alexandre Oliva wrote:
>
> On Aug 2, 2022, Eric Gallager wrote:
>
> > On Tue, Aug 2, 2022 at 1:24 AM Alexandre Oliva wrote:
>
> >> -elif test -x as$build_exeext; then
> >> +elif test -x as$build_exeext \
> >> + && { test "x$build_exeext" != "x" \
> >> +
On Tue, 2 Aug 2022, Richard Sandiford wrote:
> Currently SLP tries to force permute operations "down" the graph
> from loads in the hope of reducing the total number of permutes
> needed or (in the best case) removing the need for the permutes
> entirely. This patch tries to extend it as
Thanks for your response.
On 2022/08/03 16:52, Richard Sandiford wrote:
> Takayuki 'January June' Suwa via Gcc-patches writes:
>> Emitting "(clobber (reg X))" before "(set (subreg (reg X)) (...))" keeps
>> data flow consistent, but it also increases register allocation pressure
>> and thus often
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106499
--- Comment #24 from Tomasz Kłoczko ---
Thank you :)
Bootstrapped and regtested on s390x-redhat-linux. Ok for master?
dg.exp=pr104612.c fails with an ICE on s390x, because copysignv2sf3
produces an insn that vsel is supposed to recognize, but can't,
because it's not defined for V2SF. Fix by defining it for all vector
modes supported by
On Tue, 2 Aug 2022, Jan Hubicka wrote:
> > On Tue, 2 Aug 2022, Aldy Hernandez wrote:
> >
> > > On Tue, Aug 2, 2022 at 1:45 PM Richard Biener wrote:
> > > >
> > > > On Tue, 2 Aug 2022, Aldy Hernandez wrote:
> > > >
> > > > > Unfortunately, this was before my time, so I don't know.
> > > > >
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105651
Jonathan Wakely changed:
What|Removed |Added
CC||hi at jdoubleu dot de
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106512
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
We produce inefficient code for some synthesized SImode conditional set
operations (i.e. ones that are not directly implemented in hardware) on
RV64. For example a piece of C code like this:
int
sleu (unsigned int x, unsigned int y)
{
return x <= y;
}
gets compiled (at `-O2') to this:
I've tried to understand how the greedy search works seeing the
bitmap dances and the split into resolve_phi. I've summarized
the intent of the algorithm as
// For further greedy searching we want to remove interesting
// names defined in BB but add ones on the PHI edges for the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99888
--- Comment #2 from Kewen Lin ---
Created attachment 53405
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53405=edit
untested patch
With the attached patch, for -fpatchable-function-entry=5,2 it gets:
foo:
.LFB0:
.cfi_startproc
The previous change to the backwards threader costing contained a
mistake that can make us reject a path based on size when the
full thread path is not know yet and the full path would be considered
hot but the partial path not yet.
Instead of adding another simple fix for this particular issue I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106512
Bug ID: 106512
Summary: String optimization underflows in
std::string::operator+ inlining
Product: gcc
Version: 12.1.1
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106069
--- Comment #26 from rsandifo at gcc dot gnu.org
---
> describes a different option on big-endian and little-endian
should have said: describes a different instruction. In other words,
the mapping of gimple to RTL operations is fixed, but
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106079
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
Hi Haochen,
on 2022/8/3 16:24, HAO CHEN GUI wrote:
> Hi,
> This patch changes the definition of TARGET_MADDLD and includes
> TARGET_POWERPC64, since maddld is a 64 bit instruction.
>
> maddld-1.c now checks "has_arch_ppc64". It depends on a patch which fixes
> empty TU problem.
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106079
--- Comment #9 from CVS Commits ---
The releases/gcc-12 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:4e5ca7ff8c9afd3c38245aa6b939cd3ae49bf1fe
commit r12-8653-g4e5ca7ff8c9afd3c38245aa6b939cd3ae49bf1fe
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106069
--- Comment #25 from rsandifo at gcc dot gnu.org
---
AIUI the rules are:
- GCC vector lane numbers always correspond to memory array indices.
For example, lane 0 always comes first in memory.
- On big-endian targets, vector loads and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106187
Richard Earnshaw changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rearnsha at gcc dot
gnu.org
1 - 100 of 122 matches
Mail list logo
