https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112392
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112392
Bug ID: 112392
Summary: `a == nonnegative ? a : abs` -> abs
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112391
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112391
Bug ID: 112391
Summary: inline-asm documentation wording for implicitly
volatile can be cause confusion
Product: gcc
Version: 14.0
Status: UNCONFIRMED
This issue is noticed when support strided load/store auto-vectorization.
Commit it as it is obvious.
gcc/ChangeLog:
* config/riscv/vector.md: Fix bug.
---
gcc/config/riscv/vector.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/config/riscv/vector.md
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112390
Bug ID: 112390
Summary: `!(A & INT_MIN) & !!(A & INT_MAX)` is not optimized to
`A > 0`
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112389
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112389
Bug ID: 112389
Summary: `(x | z) < (x >> y)` should be optimized to 0
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112388
Bug ID: 112388
Summary: clear_cache vs cores with different cache line sizes
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112387
Bug ID: 112387
Summary: RISC-V: failed to SLP INT64 gather load
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112386
Bug ID: 112386
Summary: `CMP0 && CMP1 && CMP2` is better optimized than `CMP0
& CMP1 & CMP2`
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112385
--- Comment #2 from Andrew Pinski ---
We can even do it if we know the unsigned value does not have the last bit set.
That is:
```
int f(int a, unsigned b, int c)
{
b &= 0x;
return (c >> a) ^ (b >> a);
}
```
Note clang(LLVM) does not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112263
--- Comment #11 from Ian Lance Taylor ---
vincenzo: the patch in the linked e-mail is the complete diff. There are no
changes to generated Makefile.in files.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112385
--- Comment #1 from Andrew Pinski ---
Note a more complex case like:
```
int f(int a, unsigned b, int c)
{
c &= 0x;
return (c >> a) ^ (b >> a);
}
```
Should also be optimized to:
```
int f(int a, unsigned b, int c)
{
c &= 0x;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112385
Bug ID: 112385
Summary: `(2 >> a) ^ (5 >> a)` is not optimized to `7 >> a` is
2 and 5 differ in signedness
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Hi Folks
> On 4 Nov 2023, at 17:02, Simon Wright wrote:
>
> On 3 Nov 2023, at 08:39, Arnaud Charlet wrote:
>> So without changing fundamentally the model, you can't decide dynamically
>> for the whole
>> system. Making the choice based on the current directory is pretty random,
>> since the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85592
--- Comment #2 from Andrew Pinski ---
clang support:
https://reviews.llvm.org/D153153
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77635
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112384
--- Comment #1 from Andrew Pinski ---
Oh f2 just goes to memory.
Produces:
```
and x0, x0, 3
str q0, [sp]
ldr s0, [sp, x0, lsl 2]
dup v0.4s, v0.s[0]
```
Now clang(LLVM) produces:
```
mov
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112384
Bug ID: 112384
Summary: a non-constant vec dup should be improved
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111907
Andrew Pinski changed:
What|Removed |Added
CC||haochen.jiang at intel dot com
---
Snapshot gcc-13-20231104 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20231104/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 13 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111907
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111907
Andrew Pinski changed:
What|Removed |Added
Summary|ICE: in |ICE: in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112383
Bug ID: 112383
Summary: `a&=CST; (a) != a` and `((~b) & a) & CST != 0`
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112093
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112382
Bug ID: 112382
Summary: `(a) != a` where a is known to have one known bit
set is not optimized to ((~b)>>shift) & 1
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110903
Andrew Pinski changed:
What|Removed |Added
Target Milestone|12.4|14.0
--- Comment #7 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110903
--- Comment #6 from Thomas Koenig ---
The original regression was caused by r12-4526-gd8edfadfc7a979 .
d8edfadfc7a9795b65177a50ce44fd348858e844 is the first bad commit
commit d8edfadfc7a9795b65177a50ce44fd348858e844
Author: Aldy Hernandez
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111956
--- Comment #5 from Maciej W. Rozycki ---
Hmm, this seems awkward to me. It won't work AFAICT with the usual
native bootstrap environment, where you just run:
$ /path/to/configure && make bootstrap
and it won't work where you have an old
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112381
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112381
--- Comment #6 from Kostadin ---
(In reply to Andrew Pinski from comment #5)
> (In reply to Kostadin from comment #4)
> > This is the first commit where it doesn't ICE. I reverted it from master,
> > and it did start ICEing again.
>
> Does the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112380
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-11-04
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112380
--- Comment #7 from Andrew Pinski ---
(In reply to Sam James from comment #6)
> bisect says:
>
> commit r14-4612-g6decda1a35be57
> Author: Richard Biener
> Date: Thu Oct 12 11:34:57 2023 +0200
>
> tree-optimization/111779 - Handle some
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112381
--- Comment #5 from Andrew Pinski ---
(In reply to Kostadin from comment #4)
> This is the first commit where it doesn't ICE. I reverted it from master,
> and it did start ICEing again.
Does the ICE start at f08ca5903c7 ? If so this was the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111810
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-11-04
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112380
Sam James changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112381
--- Comment #4 from Kostadin ---
This is the first commit where it doesn't ICE. I reverted it from master, and
it did start ICEing again.
commit r14-5001-g8111b5c23bd14f
Author: Haochen Gui
Date: Mon Oct 30 10:59:51 2023 +0800
Expand:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111816
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111809
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-11-04
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111956
Gaius Mulley changed:
What|Removed |Added
CC||gaius at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112269
Andrew Pinski changed:
What|Removed |Added
Keywords|needs-reduction |
--- Comment #10 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112288
Patrick Palka changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112379
Sergei Trofimovich changed:
What|Removed |Added
Resolution|--- |FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112379
--- Comment #2 from CVS Commits ---
The master branch has been updated by Sergei Trofimovich :
https://gcc.gnu.org/g:9eef85a0276a0a118b76ce2da00861b75e9a3012
commit r14-5125-g9eef85a0276a0a118b76ce2da00861b75e9a3012
Author: Sergei Trofimovich
On Sat, Nov 4, 2023 at 9:41 AM Enrico via Gcc wrote:
>
> Hello,
>
>
> for a custom architecture I am working on, I would like to entirely disable
> the usage of hardware floating point instructions in favor of library
> methods on demand.
>
> I need advice on what is the best strategy to do this.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112381
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112380
--- Comment #5 from Andrew Pinski ---
```
Trying 25, 31, 32 -> 34:
25: strict_low_part(r114:TI#0)=r102:QI
REG_DEAD r102:QI
31: {r131:SI=r130:SI&0x1f800;clobber flags:CC;}
REG_DEAD r130:SI
REG_UNUSED flags:CC
32:
Hello Richard:
Below are the performance numbers on CPU 2017 benchmarks with and without
register pressure
changes for code sinking.
INT Benchmarks:
With register pressure code sinking changes:
Estimated Estimated
Base Base
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112380
--- Comment #4 from Sam James ---
(In reply to Sam James from comment #3)
> might not be a 14 regression, I need to build older gccs with more checking
ok, it is a 14 regression
On Sat, 2023-11-04 at 16:23 +, Sergei Trofimovich wrote:
> From: Sergei Trofimovich
>
> Without the change `./configure --enable-checking=release` bootstrap
> fails as:
>
> gcc/gcc-urlifier.cc:100:1: error:
> 'get_url_suffix_for_quoted_text()'
> defined but not used
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112377
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112381
--- Comment #3 from Sam James ---
(In reply to Sam James from comment #0)
> Interestingly, it is the same source file as
> in PR112380 (which still occurs on trunk).
sorry, I lied here, just similar names and I skimmed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112381
--- Comment #2 from Sam James ---
```
[...]
In file included from ../mesa-23.2.1/src/util/u_debug.h:49,
from ../mesa-23.2.1/src/util/format/u_format.h:35,
from ../mesa-23.2.1/src/compiler/nir/nir.h:43,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112381
--- Comment #1 from Sam James ---
Created attachment 56507
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56507=edit
reduced.i
Attached reduced version. Not bothered cleaning it up b/c of that issue with it
working on trunk.
Needs gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112381
Bug ID: 112381
Summary: [14 regression] ICE when building Mesa (internal
compiler error: in lra_split_hard_reg_for)
Product: gcc
Version: 14.0
Status: UNCONFIRMED
On 3 Nov 2023, at 08:39, Arnaud Charlet wrote:
> In addition to the non portable issues already mentioned, this change isn't
> OK also
> for other reasons.
>
> Basically this function is global and decides once for all on the case
> sensitivity, while
> the case sensitiviy is on a per
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112380
Andrew Pinski changed:
What|Removed |Added
Keywords||ice-on-valid-code
Target
Hello,
for a custom architecture I am working on, I would like to entirely disable
the usage of hardware floating point instructions in favor of library
methods on demand.
I need advice on what is the best strategy to do this. My idea is to:
- create a new flag (let's say -m[no-]float-insn or
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110903
Thomas Koenig changed:
What|Removed |Added
Summary|[12/13/14 Regression] Dead |[12/13 Regression] Dead
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112379
--- Comment #1 from Sergei Trofimovich ---
Proposed trivial fix by marking helper as `ATTRIBUTE_UNUSED`:
https://gcc.gnu.org/pipermail/gcc-patches/2023-November/635194.html
From: Sergei Trofimovich
Without the change `./configure --enable-checking=release` bootstrap
fails as:
gcc/gcc-urlifier.cc:100:1: error: 'get_url_suffix_for_quoted_text()'
defined but not used [-Werror=unused-function]
This happens because the helper is used only in `ASSERT`
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112380
--- Comment #3 from Sam James ---
might not be a 14 regression, I need to build older gccs with more checking
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112380
--- Comment #2 from Sam James ---
reduced:
```
enum { TGSI_FILE_NULL };
struct ureg_src {
unsigned File : 4;
unsigned : 2;
unsigned : 2;
unsigned : 2;
unsigned : 1;
unsigned IndirectFile : 4;
unsigned IndirectSwizzle : 2;
int :
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60846
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97245
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |13.3
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97245
--- Comment #6 from CVS Commits ---
The releases/gcc-13 branch has been updated by Harald Anlauf
:
https://gcc.gnu.org/g:e6ea74b68c5904446da6050751fde97d02549d1f
commit r13-8002-ge6ea74b68c5904446da6050751fde97d02549d1f
Author: Harald Anlauf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112380
--- Comment #1 from Sam James ---
I'll try reduce it now.
grind-annotations --disable-vtable-verify
--disable-libvtv --with-zstd --with-isl --disable-isl-version-check
--enable-default-pie --enable-host-pie --enable-host-bind-now
--enable-default-ssp --with-build-config='bootstrap-O3 bootstrap-lto
bootstrap-cet'
Thread model: posix
Supported LTO compression algor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112368
Francois-Xavier Coudert changed:
What|Removed |Added
Status|NEW |RESOLVED
ompression algorithms: zlib
gcc version 14.0.0 20231104 (experimental) (GCC)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112378
--- Comment #1 from Rimvydas (RJ) ---
The -fanalyzer does not seem to handle glibc __CONST_SOCKADDR_ARG definitions
with transparent_unions that are used under -D_GNU_SOURCE (__USE_GNU).
Minimal reduced testcase:
$ cat test_sockaddr.c
struct
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112378
Bug ID: 112378
Summary: Missing -fanalizer diagnostics with glibc
under _GNU_SOURCE
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112349
康桓瑋 changed:
What|Removed |Added
CC||hewillk at gmail dot com
--- Comment #2 from 康桓瑋
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111930
--- Comment #4 from Richard Sandiford ---
(In reply to Xi Ruoyao from comment #3)
> Note that now we have only 2 weeks before GCC 14 stage 1 ends.
Yeah, I'm aware. :)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111930
--- Comment #3 from Xi Ruoyao ---
(In reply to Richard Sandiford from comment #1)
> We're aiming to add SME and SME2 support in GCC 14, hopefully by the end of
> the year.
Note that now we have only 2 weeks before GCC 14 stage 1 ends.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98541
uecker at gcc dot gnu.org changed:
What|Removed |Added
Known to fail||11.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112377
uecker at gcc dot gnu.org changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112377
uecker at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2023-11-04
On Sat, 28 Oct 2023 at 14:15, Feng Jisen wrote:
>
> This patch remove a redundant partial specialization in class _Nth_type.
Thanks for the patch, I've pushed it to trunk now.
>
> For the original metafunction _Nth_type code,
> # 0
> template
> struct _Nth_type<0, _Tp0, _Rest...>
>
Tested x86_64-linux. Pushed to trunk.
Probably worth backporting after some time on trunk.
-- >8 --
Use strerror_r instead of strerror when available, due to the latter not
being thread-safe. This is complicated by Glibc providing a GNU-specific
strerror_r which is not compatible with POSIX
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110133
--- Comment #3 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:51f94778b45514992a716b0b2d7a87244e6f0018
commit r14-5123-g51f94778b45514992a716b0b2d7a87244e6f0018
Author: Jonathan Wakely
Pushed to trunk.
-- >8 --
The name "_N" is listed as a reserved name on Solaris, so we shouldn't
use it as an example of our naming conventions.
libstdc++-v3/ChangeLog:
* doc/xml/manual/appendix_contributing.xml: Replace example that
uses a BADNAME.
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112269
--- Comment #9 from Jonathan Wakely ---
(In reply to Patrick Palka from comment #5)
> I can't reproduce any of these testsuite failures on trunk with x86_64
> -m32... could you provide a preprocessed source file perhaps?
The libstdc++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112347
--- Comment #21 from David Binderman ---
(In reply to Martin Uecker from comment #16)
> I agree that the C++ should have this warning as well, although it seems
> less important there. This would be an enhancement request for the C++ FE.
See
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112377
Bug ID: 112377
Summary: Implement -Walloc-size in c++
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Hi!
This patch adds omp::decl support which has been added recently for
C++ also to C.
Bootstrapped/regtested on x86_64-linux and i686-linux, committed to
trunk.
2023-11-04 Jakub Jelinek
* c-parser.h (c_maybe_parse_omp_decl): Declare.
* c-parser.cc (struct c_parser): Add
Hi!
The following patch adds support for attribute syntax which we have in C++11
and above since GCC 12 also for C, where OpenMP standard is going to add it
in OpenMP 6.0.
Bootstrapped/regtested on x86_64-linux and i686-linux, committed to trunk.
2023-11-04 Jakub Jelinek
gcc/c/
*
Hi Martin,
This looks to be 'obvious' and is certainly OK for mainline. Backport if
you wish.
Thanks
Paul
On Fri, 3 Nov 2023 at 12:54, Martin Jambor wrote:
> Hi,
>
> when developing an otherwise unrelated patch I've discovered that the
> fnspec for the Fortran library function
I'm unfortunately going down a rabbit hole again.
--function.h:608
```
/* If pointers to member functions use the least significant bit to
indicate whether a function is virtual, ensure a pointer
to this function will have that bit clear. */
#define MINIMUM_METHOD_BOUNDARY \
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112376
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112376
Bug ID: 112376
Summary: [14 Regression] gcc.dg/tree-ssa/ssa-dom-thread-7.c was
not adjusted for aarch64 case
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112375
--- Comment #2 from Andrew Pinski ---
This simple patch fixes the issue but I have not tested it yet, basically it
moves the ins case before the zip:
```
diff --git a/gcc/config/aarch64/aarch64.cc b/gcc/config/aarch64/aarch64.cc
index
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112375
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112375
Bug ID: 112375
Summary: vget_set_lane_1.c fails
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: testsuite-fail
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112272
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
96 matches
Mail list logo
