https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110120
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |14.0
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110085
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.2
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110085
--- Comment #3 from CVS Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:afd87299cefd021daf0158d5b6276c37013996b9
commit r14-1541-gafd87299cefd021daf0158d5b6276c37013996b9
Author: Andrew Pinski
Date:
Configured with:
/var/tmp/portage/sys-devel/gcc-14.0.0_pre20230604/work/gcc-14-20230604/configure
--host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --prefix=/usr
--bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/14
--includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/14/include
--datadir=/usr/share/gcc-data
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110120
--- Comment #1 from Sam James ---
march is znver2.
sys-include
-fno-checking -m32
-I/var/tmp/portage/sys-devel/gcc-14.0.0_pre20230604/work/gcc-14-20230604/libstdc++-v3/../libgcc
-I/var/tmp/portage/sys-devel/gcc-14.0.0_pre20230604/work/build/x86_64-pc-linux-gnu/32/libstdc++-v3/include/x86_64-pc-linux-gnu
-I/var/tmp/portage/sys-devel/gcc-14.0.0_pre20230604/w
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110085
Andrew Pinski changed:
What|Removed |Added
URL||https://gcc.gnu.org/piperma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110119
Bug ID: 110119
Summary: RISC-V: RVV
--param=riscv-autovec-preference=fixed-vlmax ICE
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110085
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-06-05
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25790
Andrew Pinski changed:
What|Removed |Added
CC||garyfunck at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67792
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25790
Andrew Pinski changed:
What|Removed |Added
Status|ASSIGNED|NEW
Assignee|bonzini at gnu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25790
Andrew Pinski changed:
What|Removed |Added
CC||craig.powers at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39933
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39933
Andrew Pinski changed:
What|Removed |Added
CC||martin.vahi at softf1 dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106429
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110108
--- Comment #3 from Hongtao.liu ---
(In reply to Andrew Pinski from comment #1)
> So we should be using ABSU_EXPR instead of ABS for _mm_abs_epi8 I think ...
>
> That will fix the issue.
Yes, ABSU_EXPR + VIEW_CONVERT_EXPR.
And also I notice
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110057
--- Comment #8 from Ng YongXiang ---
Just added a patch to illustrate the array destruction issue. What do you
think?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110057
Ng YongXiang changed:
What|Removed |Added
CC||yongxiangng at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110089
Kewen Lin changed:
What|Removed |Added
CC||segher at gcc dot gnu.org
--- Comment #7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110117
--- Comment #6 from Andrew Pinski ---
Simplier testcase:
```
int f()
{
int t = 0;
return (t & 1) != 0;
}
```
Options are:
`-O1 -fno-tree-dominator-opts -fno-tree-vrp -fno-tree-ccp -fno-tree-forwprop
-fno-tree-fre -fno-tree-copy-prop` .
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110118
Hongtao.liu changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80040
Hongtao.liu changed:
What|Removed |Added
CC||crazylht at gmail dot com
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110118
Bug ID: 110118
Summary: Miss CSE optimization for vptest after
r14-1466-g3635e8c67e13e3da7e1e23a617dd9952218e93e0
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110059
d_vampile changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110067
--- Comment #12 from Hongtao.liu ---
(In reply to Sam James from comment #11)
> (In reply to Hongtao.liu from comment #9)
> > Fixed.
>
> OK to close?
Yes.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110117
--- Comment #5 from Andrew Pinski ---
Created attachment 55255
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55255=edit
Patch which fixes this
I am going to split this patch into 2, one for the do_store_flag change and one
for the patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54089
--- Comment #59 from Oleg Endo ---
(In reply to Alexander Klepikov from comment #58)
>
> Ouch. That's a real problem. Short loops can become slower on about 10%. But
> is it possible to detect a loop during expand pass? It looks like basic
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31584
Richard Smith changed:
What|Removed |Added
CC||richard-gccbugzilla@metafoo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110117
--- Comment #4 from Andrew Pinski ---
This was "fixed" by r14-1534-g908e5ab5c11c64 as we don't have a nonzero bits on
_5 in :
# RANGE [irange] int [-2147483647, +INF]
_4 = 0;
_5 = _4 & 1;
_39 = _5 != 0;
Since we don't have a non-zero
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110116
Andrew Pinski changed:
What|Removed |Added
Summary|ICE on valid code at -O3 on |[12/13/14 Regression] ICE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110117
--- Comment #3 from Andrew Pinski ---
Anyways imode should just be operand_mode really.
But that does not solve the issue either because extract_bit_field does not
know how to handle const_int :(.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110117
--- Comment #2 from Andrew Pinski ---
_4 = 0;
_5 = _4 & 1;
_39 = _5 != 0;
The reason why it worked before was that when creating trees, it simplify down
to 0 and then expand that. Now we are expanding directly to rtl, we get:
(const_int
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110117
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Target Milestone|---
k
--enable-sanitizers --enable-languages=c,c++ --disable-werror
--disable-multilib
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 14.0.0 20230604 (experimental) [master r14-924-gd709841ae0f] (GCC)
[585] %
[585] % gcctk -O1 -ftree-vrp -fno-tree-ccp -fno-tree-forwprop smal
/software/local/gcc-trunk
--enable-sanitizers --enable-languages=c,c++ --disable-werror
--disable-multilib
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 14.0.0 20230604 (experimental) [master r14-924-gd709841ae0f] (GCC)
[636] %
[636] % gcctk -O3 small.c
small.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110115
--- Comment #4 from Andrew Pinski ---
And yes -fstack-reuse=none fixes the issue.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110115
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110115
Andrew Pinski changed:
What|Removed |Added
Keywords||wrong-code
Component|c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110115
--- Comment #1 from Andrew Pinski ---
Partition 0: size 24 align 16
k h
That is definitely wrong.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110115
Bug ID: 110115
Summary: Wrong code at -O1 on x86_64-linux-gnu
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85605
Andrew Pinski changed:
What|Removed |Added
Status|RESOLVED|ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78352
--- Comment #20 from Iain Sandoe ---
(In reply to Sergey Fedorov from comment #19)
> (In reply to Iain Sandoe from comment #1)
> > Just to add one note, which is that Apple's gcc-4.2.1 implementation for
> > blocks was not actually submitted
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110114
Andrew Pinski changed:
What|Removed |Added
Keywords||ice-on-invalid-code
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78352
--- Comment #19 from Sergey Fedorov ---
(In reply to Iain Sandoe from comment #1)
> Just to add one note, which is that Apple's gcc-4.2.1 implementation for
> blocks was not actually submitted (and therefore doesn't exist on an FSF
> server);
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110114
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30829
Roger Sayle changed:
What|Removed |Added
CC||roger at nextmovesoftware dot
com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54089
--- Comment #58 from Alexander Klepikov
---
> Another thing ... the reason why it's desirable to expand into the libcall
> earlier is to allow hoisting the function call address outside of loops and
> things like that.
Ouch. That's a real
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100607
--- Comment #15 from CVS Commits ---
The releases/gcc-11 branch has been updated by Harald Anlauf
:
https://gcc.gnu.org/g:37fdec3b7feca378693b3f12dbee422752176b24
commit r11-10844-g37fdec3b7feca378693b3f12dbee422752176b24
Author: Steve Kargl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31985
Roger Sayle changed:
What|Removed |Added
CC||roger at nextmovesoftware dot
com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100607
--- Comment #14 from CVS Commits ---
The releases/gcc-12 branch has been updated by Harald Anlauf
:
https://gcc.gnu.org/g:59a264d5d8bb3fb73557aafc21319fd4fa6b1ab4
commit r12-9677-g59a264d5d8bb3fb73557aafc21319fd4fa6b1ab4
Author: Steve Kargl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110114
Bug ID: 110114
Summary: ICE on calling overloaded function in case of
incomplete argument type
Product: gcc
Version: 13.1.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110113
--- Comment #2 from Witold Baryluk ---
Also FYI, I was not able to trigger this on DMD64 D Compiler v2.104.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110113
--- Comment #1 from Witold Baryluk ---
BTW. Adding return statement in `raytrace`, does not change anything:
```
user@debian:~$ gdc-13 -c -fpreview=dip1021 lup.d
user@debian:~$ gdc-13 -c -fpreview=dip1021 lup.d
user@debian:~$ gdc-13 -c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110113
Bug ID: 110113
Summary: gdc -fpreview=dip1021 crash in d/dmd/root/aav.d:127
dmd_aaGetRvalue from DsymbolTable::lookup(Identifier
const*)
Product: gcc
Version:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110104
Roger Sayle changed:
What|Removed |Added
CC||roger at nextmovesoftware dot
com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110109
Jeffrey A. Law changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110109
--- Comment #3 from CVS Commits ---
The master branch has been updated by Pan Li :
https://gcc.gnu.org/g:a96ba6b958a00ad59c43cae10be65b263b5d0d2d
commit r14-1531-ga96ba6b958a00ad59c43cae10be65b263b5d0d2d
Author: Juzhe-Zhong
Date: Sun Jun 4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110102
--- Comment #4 from Arthur O'Dwyer ---
I came across the `Widget` bug in the course of writing (and it's now mentioned
in) this blog post on value semantics and PMR:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110112
Tim Lange changed:
What|Removed |Added
CC||tlange at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110112
Bruno Haible changed:
What|Removed |Added
Host||x86_64-linux-gnu
Known to fail|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110112
Bug ID: 110112
Summary: [11/12/13 Regression] gcc -fanalyzer takes an
excessive amount of time
Product: gcc
Version: 13.1.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110083
--- Comment #3 from CVS Commits ---
The master branch has been updated by Roger Sayle :
https://gcc.gnu.org/g:8ab9fb6b8e05cf9acca7bd8282979ede53524cf1
commit r14-1528-g8ab9fb6b8e05cf9acca7bd8282979ede53524cf1
Author: Roger Sayle
Date: Sun
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109973
--- Comment #9 from CVS Commits ---
The master branch has been updated by Roger Sayle :
https://gcc.gnu.org/g:8ab9fb6b8e05cf9acca7bd8282979ede53524cf1
commit r14-1528-g8ab9fb6b8e05cf9acca7bd8282979ede53524cf1
Author: Roger Sayle
Date: Sun
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110061
--- Comment #15 from Xi Ruoyao ---
(In reply to Wilco from comment #14)
> (In reply to Wilco from comment #13)
> > (In reply to Xi Ruoyao from comment #12)
> > > (In reply to Wilco from comment #11)
> > >
> > > > > Then the compiler (and the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110103
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110102
--- Comment #3 from Jonathan Wakely ---
In both examples we do still use allocator_traits::construct to initialize the
elements, which is what matters for correct behaviour of sensible programs.
For the first one we call construct(A*, int&&)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110111
Bug ID: 110111
Summary: bool patterns that should produce a?b:c
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109541
--- Comment #15 from Sam James ---
Okay. I couldn't hit it on some native machines until I rebuilt with more
checking, but maybe that was a fluke.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109541
--- Comment #14 from Eric Botcazou ---
> By the way, I think this needs --enable-checking=rtl, which is maybe why you
> couldn't hit it before.
No, that's incorrect. You need a properly configured compiler instead.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109712
--- Comment #12 from Carlos Galvez ---
I just tested latest and greatest trunk (git commit
2415024e0f81f8c09bf08f947c790b43de9d0bbc) and the problem persists. Slightly
different line numbers but essentially same backtrace:
#0
71 matches
Mail list logo
