[Bug target/113030] parsecpu.awk's chkarch/chkcpu commands is broken for aliases

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113030

Andrew Pinski  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Assignee|unassigned at gcc dot gnu.org  |pinskia at gcc dot 
gnu.org

--- Comment #5 from Andrew Pinski  ---
Patch posted:
https://gcc.gnu.org/pipermail/gcc-patches/2024-January/643549.html

[Bug c/109708] [c, doc] wdangling-pointer example broken

2024-01-20 Thread sandra at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109708

sandra at gcc dot gnu.org changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from sandra at gcc dot gnu.org ---
Fixed.

[Bug c/109708] [c, doc] wdangling-pointer example broken

2024-01-20 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109708

--- Comment #3 from GCC Commits  ---
The master branch has been updated by Sandra Loosemore :

https://gcc.gnu.org/g:29f931e39f2be86b454a8264b1cd42e4ca3cdcd7

commit r14-8314-g29f931e39f2be86b454a8264b1cd42e4ca3cdcd7
Author: Sandra Loosemore 
Date:   Sun Jan 21 02:36:19 2024 +

Clean up examples for -Wdangling-pointer [PR109708]

gcc/ChangeLog
PR c/109708
* doc/invoke.texi (Warning Options): Fix broken example and
clean up/reorganize the others.  Also describe what the short-form
options mean.

[Bug ipa/109112] [[assume(...)]] is not taken into account for structs

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109112

Andrew Pinski  changed:

   What|Removed |Added

 CC||eric-bugs at omnifarious dot 
org

--- Comment #9 from Andrew Pinski  ---
*** Bug 113527 has been marked as a duplicate of this bug. ***

[Bug ipa/113527] Missed optimization [[assume]] attribute

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113527

Andrew Pinski  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Andrew Pinski  ---
Dup of bug 109112, that is the problem is similar for many other things.

*** This bug has been marked as a duplicate of bug 109112 ***

[Bug tree-optimization/113527] Missed optimization [[assume]] attribute

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113527

Andrew Pinski  changed:

   What|Removed |Added

   Keywords||missed-optimization
   Severity|normal  |enhancement
  Component|c++ |tree-optimization

[Bug c++/113527] New: Missed optimization [[assume]] attribute

2024-01-20 Thread eric-bugs at omnifarious dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113527

Bug ID: 113527
   Summary: Missed optimization [[assume]] attribute
   Product: gcc
   Version: 14.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c++
  Assignee: unassigned at gcc dot gnu.org
  Reporter: eric-bugs at omnifarious dot org
  Target Milestone: ---

This code https://godbolt.org/z/jeYGcr5sv still generates all the exception
handling code. It treats the assume attribute more like 'likely' than 'assume'.
It's supposed to be undefined behavior for the assumption to be false.

Here is the code replicated here:

#include 

struct Potato
{
explicit Potato(int);
Potato(const Potato & other) noexcept;
};

using V = std::variant;

template 
struct overloaded : Ts_... { using Ts_::operator()...; };

auto f(const V & v) -> int
{
[[assume(! v.valueless_by_exception())]];
return visit(overloaded{
[](int) { return 144; },
[](double) { return 27; },
[](const Potato &) { return 50; }
}, v);
}

You can make the exception handling code go away by simply using "if
(v.valueless_by_exception())" and returning some random value in the false
case. But, if the spirit of the keyword is to be observed, you should be fine
just doing a straight up table lookup and using the result without even
checking the type tag at all.

[Bug tree-optimization/110935] Missed BB reduction vectorization because of missed eliding of a permute

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110935

Andrew Pinski  changed:

   What|Removed |Added

   Last reconfirmed||2024-01-21
 Ever confirmed|0   |1
 CC||pinskia at gcc dot gnu.org
 Status|UNCONFIRMED |NEW

--- Comment #4 from Andrew Pinski  ---
Confirmed.  I noticed the PERM issue when I was working on adding V4HI support
to the aarch64 backend.  I had to add PERM support for V4HI but it was not
obvious at the time why. This explains it.

[Bug tree-optimization/113239] [13/14 regression] After 822a11a1e64, bogus -Warray-bounds warnings in std::vector

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113239

--- Comment #6 from Andrew Pinski  ---
Why the warning only happens with the 2 elements in frame_t, I have no idea
really since there seems not to be any changes in the final IR (except for an
extra load/store for those 2 elements).

[Bug tree-optimization/113239] [13/14 regression] After 822a11a1e64, bogus -Warray-bounds warnings in std::vector

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113239

--- Comment #5 from Andrew Pinski  ---
Note the missed optimization was there in GCC 12, just the diagnostic was not.

We have:
```
  _4 = MEM[(const unsigned char * const &)current_frame__2(D) + 24];
  _7 = MEM[(const unsigned char * const &)current_frame__2(D) + 16];
  if (_4 == _7)
goto ; [17.43%]
  else
goto ; [82.57%]

   [local count: 187153200]:
...
  MEM  [(unsigned char * *)_5(D) + 16B] = { 0, 0
};
  MEM[(struct _Vector_base *)_5(D) + 16B]._M_impl.D.21112._M_end_of_storage =
0B;
  _21 = MEM[(const unsigned char * const &)current_frame__2(D) + 24];
  _22 = MEM[(const unsigned char * const &)current_frame__2(D) + 16];
  _Num_23 = _21 - _22;
```

But based on the original condition (and the stores to offset of _5 [which
technically cannot alias current_frame__2]), _Num_23 will be 0.

What g:822a11a1e642e0abe92a996e7033a5066905a447 does is just add an extra if
statement where we get:
```
  if (_Num_24 > 1)
goto ; [90.00%]
  else
goto ; [10.00%]

   [local count: 156478790]:
  _Num.5_28 = (long unsigned int) _Num_24;
  __builtin_memmove (0B, _22, _Num.5_28);
  goto ; [100.00%]

   [local count: 17386533]:
  if (_Num_24 == 1)
goto ; [34.00%]
  else
goto ; [66.00%]

   [local count: 5911421]:
  MEM[(unsigned char *)0B] ={v} 0; /// << This is causing the warning
  __builtin_trap ();
```

Instead of just:
```
  if (_Num_23 != 0)
goto ; [33.00%]
  else
goto ; [67.00%]

   [local count: 57375556]:
  _Num.4_24 = (long unsigned int) _Num_23;
  __builtin_memmove (0B, _22, _Num.4_24);

```

[Bug target/113526] [14 Regression] gcc.target/arm/asm-flag-1.c fails since gcc-14-7248-g76bc70387d9

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113526

Andrew Pinski  changed:

   What|Removed |Added

   Keywords||inline-asm, ra,
   ||rejects-valid
Summary|[14 Regression ARM] |[14 Regression]
   |gcc.target/arm/asm-flag-1.c |gcc.target/arm/asm-flag-1.c
   |fails since |fails since
   |gcc-14-7248-g76bc70387d9|gcc-14-7248-g76bc70387d9
   Target Milestone|--- |14.0

[Bug target/113526] New: [14 Regression ARM] gcc.target/arm/asm-flag-1.c fails since gcc-14-7248-g76bc70387d9

2024-01-20 Thread thiago.bauermann at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113526

Bug ID: 113526
   Summary: [14 Regression ARM] gcc.target/arm/asm-flag-1.c fails
since gcc-14-7248-g76bc70387d9
   Product: gcc
   Version: 14.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: thiago.bauermann at linaro dot org
CC: vmakarov at redhat dot com
  Target Milestone: ---
Target: arm-none-eabi

Created attachment 57180
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57180=edit
gcc.log showing failures in gcc.target/arm/asm-flag-1.c

After commit 76bc70387d93 ("[PR113354][LRA]: Fixing LRA failure on building
MIPS GCC"), the following failures started appearing on --target=arm-none-eabi:

=== gcc tests ===

Running gcc:gcc.target/arm/arm.exp ...
FAIL: gcc.target/arm/asm-flag-1.c (test for excess errors)
UNRESOLVED: gcc.target/arm/asm-flag-1.c scan-assembler movcc
UNRESOLVED: gcc.target/arm/asm-flag-1.c scan-assembler movcs
UNRESOLVED: gcc.target/arm/asm-flag-1.c scan-assembler moveq
UNRESOLVED: gcc.target/arm/asm-flag-1.c scan-assembler movge
UNRESOLVED: gcc.target/arm/asm-flag-1.c scan-assembler movgt
UNRESOLVED: gcc.target/arm/asm-flag-1.c scan-assembler movhi
UNRESOLVED: gcc.target/arm/asm-flag-1.c scan-assembler movle
UNRESOLVED: gcc.target/arm/asm-flag-1.c scan-assembler movls
UNRESOLVED: gcc.target/arm/asm-flag-1.c scan-assembler movmi
UNRESOLVED: gcc.target/arm/asm-flag-1.c scan-assembler movne
UNRESOLVED: gcc.target/arm/asm-flag-1.c scan-assembler movpl
UNRESOLVED: gcc.target/arm/asm-flag-1.c scan-assembler movvc
UNRESOLVED: gcc.target/arm/asm-flag-1.c scan-assembler movvs

The test fails because GCC can't compile asm-flag-1.c anymore:

spawn -ignore SIGHUP /tmp/arm-none-eabi/bin/arm-none-eabi-gcc
/tmp/combined-tree-src/gcc/testsuite/gcc.target/arm/asm-flag-1.c
-fdiagnostics-plain-output -O -ffat-lto-objects -fno-ident -S -o asm-flag-1.s
/tmp/combined-tree-src/gcc/testsuite/gcc.target/arm/asm-flag-1.c: In function
'f':
/tmp/combined-tree-src/gcc/testsuite/gcc.target/arm/asm-flag-1.c:12:3: error:
'asm' operand has impossible constraints or there are not enough registers
compiler exited with status 1
FAIL: gcc.target/arm/asm-flag-1.c (test for excess errors)
Excess errors:
/tmp/combined-tree-src/gcc/testsuite/gcc.target/arm/asm-flag-1.c:12:3: error:
'asm' operand has impossible constraints or there are not enough registers

gcc.target/arm/asm-flag-1.c: output file does not exist
UNRESOLVED: gcc.target/arm/asm-flag-1.c scan-assembler movne
gcc.target/arm/asm-flag-1.c: output file does not exist
UNRESOLVED: gcc.target/arm/asm-flag-1.c scan-assembler moveq
gcc.target/arm/asm-flag-1.c: output file does not exist
UNRESOLVED: gcc.target/arm/asm-flag-1.c scan-assembler movcs
gcc.target/arm/asm-flag-1.c: output file does not exist
UNRESOLVED: gcc.target/arm/asm-flag-1.c scan-assembler movcc
gcc.target/arm/asm-flag-1.c: output file does not exist
UNRESOLVED: gcc.target/arm/asm-flag-1.c scan-assembler movmi
gcc.target/arm/asm-flag-1.c: output file does not exist
UNRESOLVED: gcc.target/arm/asm-flag-1.c scan-assembler movpl
gcc.target/arm/asm-flag-1.c: output file does not exist
UNRESOLVED: gcc.target/arm/asm-flag-1.c scan-assembler movvs
gcc.target/arm/asm-flag-1.c: output file does not exist
UNRESOLVED: gcc.target/arm/asm-flag-1.c scan-assembler movvc
gcc.target/arm/asm-flag-1.c: output file does not exist
UNRESOLVED: gcc.target/arm/asm-flag-1.c scan-assembler movhi
gcc.target/arm/asm-flag-1.c: output file does not exist
UNRESOLVED: gcc.target/arm/asm-flag-1.c scan-assembler movls
gcc.target/arm/asm-flag-1.c: output file does not exist
UNRESOLVED: gcc.target/arm/asm-flag-1.c scan-assembler movge
gcc.target/arm/asm-flag-1.c: output file does not exist
UNRESOLVED: gcc.target/arm/asm-flag-1.c scan-assembler movls
gcc.target/arm/asm-flag-1.c: output file does not exist
UNRESOLVED: gcc.target/arm/asm-flag-1.c scan-assembler movgt
gcc.target/arm/asm-flag-1.c: output file does not exist
UNRESOLVED: gcc.target/arm/asm-flag-1.c scan-assembler movle

I tested on today's trunk (commit 036623196777) and the failures are still
present. I'm attaching the gcc.log file.

Here's how to reproduce on an x86_64-linux machine:

1. First, create a combined tree:

$ mkdir /tmp/combined-tree-src /tmp/combined-tree-build
$ cd ~/src/newlib-cygwin && find . -print | cpio -pdlm /tmp/combined-tree-src
$ cd ~/src/binutils-gdb && find . -print | cpio -pdlmu /tmp/combined-tree-src
$ cd ~/src/gcc && find . -print | cpio -pdlmu /tmp/combined-tree-src

2. Then build and install the cross GCC:

$ cd /tmp/combined-tree-build
$ /tmp/combined-tree-src/configure \
SHELL=/bin/bash \
--with-gnu-as \
--with-gnu-ld \
--disable-libmudflap \
--enable-lto \
--enable-shared \
--without-included-gettext \
--enable-nls \
--with-system-zlib 

[Bug c/109708] [c, doc] wdangling-pointer example broken

2024-01-20 Thread sandra at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109708

--- Comment #2 from sandra at gcc dot gnu.org ---
I was wondering if some subsequent patch might have caused the first example to
regress rather than this being a documentation bug, but it did not give a
diagnostic at the time the -Wdangling-pointer support was committed, either. 
I'll fiddle with the example a bit to make it better illustrate the difference
between level 1 and level 2, as well as making it work.

[Bug fortran/82943] [F03] Error with type-bound procedure of parametrized derived type

2024-01-20 Thread sgk at troutmask dot apl.washington.edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82943

--- Comment #17 from Steve Kargl  ---
On Sat, Jan 20, 2024 at 09:37:17PM +, jvdelisle at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82943
> 
> --- Comment #16 from Jerry DeLisle  ---
> (In reply to Alexander Westbrooks from comment #15)
> > Created attachment 57176 [details]
> > Proposed Patch to fix PR82943, PR86148, PR86268
> 
> I am attempting to roll with this. Steve, do you know where the copyright
> assignment forms are? I a,m hunting for them and I asked on the gcc IRC 
> channel
> as well.
> 

I beleive that FSF assignments are not public.
It's been along since I dealt with someone 
getting an assignment.  I recall asking someone
on the GCC steering committee for confirmation.

I haven't dealt with the DCO method.

[Bug web/113525] [11/12/13/14 Regression] GCC does not recognize "-fdump-rtl-sibling" command line option

2024-01-20 Thread mikolajpirog at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113525

Mikołaj Piróg  changed:

   What|Removed |Added

  Component|middle-end  |web

--- Comment #3 from Mikołaj Piróg  ---
I understand, this explains a lot

[Bug middle-end/113525] [11/12/13/14 Regression] GCC does not recognize "-fdump-rtl-sibling" command line option

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113525

Andrew Pinski  changed:

   What|Removed |Added

  Known to fail||4.8.0
 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1
   Last reconfirmed||2024-01-20
  Component|other   |middle-end
Summary|GCC does not recognize  |[11/12/13/14 Regression]
   |"-fdump-rtl-sibling"|GCC does not recognize
   |command line option |"-fdump-rtl-sibling"
   ||command line option
   Target Milestone|--- |11.5

--- Comment #2 from Andrew Pinski  ---
It was removed in r0-115834-gbe147e848b387d for GCC 4.8.0 .


unshare was also removed at the same time too.

Confirmed. Just a documentation not being in sync with the source.


Note seqabstr was also removed at r0-92254-g824523999285e7 (for 4.5.0).

[Bug other/113525] GCC does not recognize "-fdump-rtl-sibling" command line option

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113525

Andrew Pinski  changed:

   What|Removed |Added

   Keywords||documentation

--- Comment #1 from Andrew Pinski  ---
The pass named sibling was removed a long time ago but the documentation was
not updated ...

[Bug fortran/57360] Implement a warning for implied save

2024-01-20 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57360

kargl at gcc dot gnu.org changed:

   What|Removed |Added

 CC||kargl at gcc dot gnu.org

--- Comment #6 from kargl at gcc dot gnu.org ---
With this patch, 

diff --git a/gcc/fortran/decl.cc b/gcc/fortran/decl.cc
index 503ecb8d9b5..abb3579893f 100644
--- a/gcc/fortran/decl.cc
+++ b/gcc/fortran/decl.cc
@@ -2278,7 +2278,12 @@ add_init_expr_to_sym (const char *name, gfc_expr
**initp, locus *var_locus)

   sym->value = init;
   if (sym->attr.save == SAVE_NONE)
-   sym->attr.save = SAVE_IMPLICIT;
+   {
+ sym->attr.save = SAVE_IMPLICIT;
+ if (warn_surprising)
+   gfc_warning (OPT_Wsurprising, "Entity %qs at %L has an implicit "
+ "SAVE attribute", sym->name, >declared_at);
+   }
   *initp = NULL;
 }

I see

% gfcx -o z a.f90 -Wsurprising && ./z
a.f90:2:13:

2 |  integer :: i=1
  | 1
Warning: Entity ‘i’ at (1) has an implicit SAVE attribute [-Wsurprising]
   1

[Bug other/113525] New: GCC does not recognize "-fdump-rtl-sibling" command line option

2024-01-20 Thread mikolajpirog at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113525

Bug ID: 113525
   Summary: GCC does not recognize "-fdump-rtl-sibling" command
line option
   Product: gcc
   Version: 13.2.1
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: other
  Assignee: unassigned at gcc dot gnu.org
  Reporter: mikolajpirog at gmail dot com
  Target Milestone: ---

My GCC config: 
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/13.2.1/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /build/gcc/src/gcc/configure
--enable-languages=ada,c,c++,d,fortran,go,lto,objc,obj-c++ --enable-bootstrap
--prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man
--infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/
--with-build-config=bootstrap-lto --with-linker-hash-style=gnu
--with-system-zlib --enable-__cxa_atexit --enable-cet=auto
--enable-checking=release --enable-clocale=gnu --enable-default-pie
--enable-default-ssp --enable-gnu-indirect-function --enable-gnu-unique-object
--enable-libstdcxx-backtrace --enable-link-serialization=1
--enable-linker-build-id --enable-lto --enable-multilib --enable-plugin
--enable-shared --enable-threads=posix --disable-libssp --disable-libstdcxx-pch
--disable-werror
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.2.1 20230801 (GCC) 

Per section 3.18 of GCC manual, GCC should recognize the "-fdump-rtl-sibling"
option. When I try to invoke this option, GCC gives my following error: "
g++ -fdump-rtl-sibling test.cc
cc1plus: error: unrecognized command-line option ‘-fdump-rtl-sibling’
"

I am unsure to which component this sort of bugs should go, so I file this
under "other" category.

[Bug fortran/82943] [F03] Error with type-bound procedure of parametrized derived type

2024-01-20 Thread jvdelisle at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82943

--- Comment #16 from Jerry DeLisle  ---
(In reply to Alexander Westbrooks from comment #15)
> Created attachment 57176 [details]
> Proposed Patch to fix PR82943, PR86148, PR86268

I am attempting to roll with this. Steve, do you know where the copyright
assignment forms are? I a,m hunting for them and I asked on the gcc IRC channel
as well.

[Bug other/86656] [meta-bug] Issues found with -fsanitize=address

2024-01-20 Thread mikael at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86656
Bug 86656 depends on bug 111291, which changed state.

Bug 111291 Summary: ASAN error: heap-use-after-free gcc/fortran/parse.cc:359 in 
decode_statement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111291

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

[Bug fortran/111291] ASAN error: heap-use-after-free gcc/fortran/parse.cc:359 in decode_statement

2024-01-20 Thread mikael at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111291

Mikael Morin  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED

--- Comment #6 from Mikael Morin  ---
Fixed for gfortran 14.
Closing.

[Bug ipa/113490] [14 Regression] ICE: in propagate_vals_across_arith_jfunc, at ipa-cp.cc:2425 at -O3 since r14-285

2024-01-20 Thread jamborm at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113490

--- Comment #5 from Martin Jambor  ---
I have proposed a fix on the mailing list: 
https://inbox.sourceware.org/gcc-patches/ri6cytv3eyy.fsf@/T/#u

[Bug other/94629] 10 issues located by the PVS-studio static analyzer

2024-01-20 Thread jamborm at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94629

--- Comment #28 from Martin Jambor  ---
(In reply to David Binderman from comment #27)
> The original article checked gcc-10.
> gcc-13 is checked in the following article:
> 
> https://pvs-studio.com/en/blog/posts/cpp/1067/
> 
> I suspect it would be most unwise if any release of gcc after 13 
> introduced new bugs that were known to pvs-studio.

And is there already a bugzilla bug about these (or should I create one)?
I believe a new one would be better than re-using this one.

[Bug c++/111410] Bogus Wdangling-reference warning with ranges pipe expression in for loop

2024-01-20 Thread mpolacek at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111410

Marek Polacek  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED

--- Comment #3 from Marek Polacek  ---
Fixed for 14.

[Bug c++/111410] Bogus Wdangling-reference warning with ranges pipe expression in for loop

2024-01-20 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111410

--- Comment #2 from GCC Commits  ---
The trunk branch has been updated by Marek Polacek :

https://gcc.gnu.org/g:7db802d972e622242d015ecd5a8cecf63e69a45a

commit r14-8307-g7db802d972e622242d015ecd5a8cecf63e69a45a
Author: Marek Polacek 
Date:   Fri Jan 19 15:27:51 2024 -0500

libstdc++: suppress -Wdangling-reference with operator| [PR111410]

It seems to me that we should exclude
std::ranges::views::__adaptor::operator|
from the -Wdangling-reference warning.  It's commonly used when handling
ranges.

PR c++/111410

libstdc++-v3/ChangeLog:

* include/std/ranges: Add #pragma to disable -Wdangling-reference
with
std::ranges::views::__adaptor::operator|.

gcc/testsuite/ChangeLog:

* g++.dg/warn/Wdangling-reference17.C: New test.

[Bug c++/104094] Alias template shown in diagnostic with wrong template parameter name

2024-01-20 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104094

--- Comment #4 from Jonathan Wakely  ---
Yeah, maybe this is just a dup of my older bug report. It's been frustrating me
for years.

And obviously I meant "hash collision" above not "has collision" :-)

[Bug other/94629] 10 issues located by the PVS-studio static analyzer

2024-01-20 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94629

--- Comment #27 from David Binderman  ---
The original article checked gcc-10.
gcc-13 is checked in the following article:

https://pvs-studio.com/en/blog/posts/cpp/1067/

I suspect it would be most unwise if any release of gcc after 13 
introduced new bugs that were known to pvs-studio.

[Bug tree-optimization/56456] [meta-bug] bogus/missing -Warray-bounds

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56456
Bug 56456 depends on bug 109744, which changed state.

Bug 109744 Summary: mesa/panvk: bogus Warray-bounds on gcc 12.2, fixed in 13 
branch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109744

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

[Bug tree-optimization/109744] mesa/panvk: bogus Warray-bounds on gcc 12.2, fixed in 13 branch

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109744

Andrew Pinski  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
   Target Milestone|--- |13.0
 Resolution|--- |FIXED

--- Comment #4 from Andrew Pinski  ---
There is not much to handle here really since the warning is heavily dependent
on optimizing including sometimes optimizing out unreachable code. In this case
it is now optimized better for GCC 13 getting rid of unreachable code which GCC
is warning about.

[Bug ipa/110705] [11/12 Regression] ICE at -O2 and above: in gimplify_modify_expr, at gimplify.cc:6255 (on GCC-12.x)

2024-01-20 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110705

--- Comment #4 from GCC Commits  ---
The trunk branch has been updated by Andrew Pinski :

https://gcc.gnu.org/g:17473a93cff5340acfc293299a2f9a5857a50909

commit r14-8306-g17473a93cff5340acfc293299a2f9a5857a50909
Author: Andrew Pinski 
Date:   Sat Jan 20 11:39:11 2024 -0800

ipa: Add testcase for already fixed case [PR110705]

This testcase was fixed with r13-1695-gb0f02eeb906b63 which
added an Ada testcase for the issue but adding a C testcase
is a good idea and that is what this does.

Committed after making sure it passes on  x86_64-linux-gnu.

PR ipa/110705

gcc/testsuite/ChangeLog:

* gcc.c-torture/compile/pr110705-1.c: New test.

Signed-off-by: Andrew Pinski 

[Bug c++/113306] constexpr cast from void* fails with typeid result target

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113306

Andrew Pinski  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1
   Last reconfirmed||2024-01-20

--- Comment #1 from Andrew Pinski  ---
Confirmed.

[Bug libgomp/113448] libgomp.c/alloc-pinned-1.c etc. XPASS

2024-01-20 Thread danglin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113448

--- Comment #2 from John David Anglin  ---
The tests fail on hppa-unknown-linux-gnu:
FAIL: libgomp.c/alloc-pinned-1.c execution test
FAIL: libgomp.c/alloc-pinned-2.c execution test
FAIL: libgomp.c/alloc-pinned-3.c execution test
FAIL: libgomp.c/alloc-pinned-4.c execution test

[Bug fortran/113152] Fortran 2023 half-cycle trigonometric functions

2024-01-20 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152

kargl at gcc dot gnu.org changed:

   What|Removed |Added

  Attachment #56949|0   |1
is obsolete||
  Attachment #56950|0   |1
is obsolete||
  Attachment #56951|0   |1
is obsolete||
  Attachment #56952|0   |1
is obsolete||
  Attachment #56956|0   |1
is obsolete||

--- Comment #12 from kargl at gcc dot gnu.org ---
Created attachment 57179
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57179=edit
Patch

Here is a new patch.  It includes an implementation for the half-cycle
trigonometric functions as well as fixes for

PR113412 -- better error message for atan(y,x)
PR113413 -- implement atand(y,x)

Here's text that may be suitable formatted for a ChangeLog.

gfortran:

* gfortran.h (gfc_isym_id): Add GFC_ISYM_ACOSPI, GFC_ISYM_ASINPI,
GFC_ISYM_ATANPI, GFC_ISYM_ATAN2PI, GFC_ISYM_COSPI, GFC_ISYM_SINPI, and
GFC_ISYM_TANPI
* intrinsic.cc (do_check): Whitespace and typo in comments.
(add_functions): Add two-argument form of ATAND.  Add half-cycle 
trigonometric functions ACOSPI, ASINPI, ATANPI, ATAN2PI, COSPI,
SINPI, and TANPI.
(sort_actual): Generate sensible error messages for two argument
versions of ATAN, ATAND, and ATANPI.
* intrinsic.h: New prototypes for gfc_simplify_acospi, 
gfc_simplify_asinpi, gfc_simplify_atanpi, gfc_simplify_atan2pi,
gfc_simplify_cospi, gfc_simplify_sinpi, gfc_simplify_tanpi,
gfc_resolve_acospi, gfc_resolve_asinpi, gfc_resolve_atanpi,
gfc_resolve_atan2pi, gfc_resolve_cospi, gfc_resolve_sinpi, and
gfc_resolve_tanpi
* intrinsic.texi: Document new functions ACOSPI, ASINPI, ATANPI,
ATAN2PI, COSPI, SINPI, and TANPI.  Put the ATAN* family of functions
in lexigraphical order.
* iresolve.cc (gfc_resolve_acospi, gfc_resolve_asinpi,
gfc_resolve_atanpi, gfc_resolve_atan2pi, gfc_resolve_cospi,
gfc_resolve_sinpi, gfc_resolve_tanpi):  New functions.
* simplify.cc (gfc_simplify_acospi, gfc_simplify_asinpi,
gfc_simplify_atanpi, gfc_simplify_atan2pi, gfc_simplify_cospi,
gfc_simplify_sinpi, gfc_simplify_tanpi): New functions.
Introduce MPFR_HALF_CYCLE macros to use MPFR half-cycle functions
if available.
* trans-intrinsic.cc: Declare asinpi, acospi, atanpi, atan2pi, sinpi, 
cospi, and tanpi as LIB_FUNCTION's.

libgfortran 

*Makefile.am: New files trigpi.c, trigpi_fallback1.c, and
trigpi_fallback2.F90
* configure.ac: Check libm for float, double, and long double
functions for asinpi, acospi, atanpi, atan2pi, sinpi, cospi, and
tanpi
* Makefile.in: Regenerated.
* config.h.in: Ditto.
* configure: Ditto.
* gfortran.map: Add GFORTRAN_14 section to expose the library
symbols.
* trigpi.c: Fallback implementations of the half-cycle trigonometric
functions.
* trigpi_fallback1.c: Fallback functions for float, double, and
long double routines if libm does provide them.
* trigpi_fallback2.F90: REAL(16)/REAL(17) fallback implementations
of the half-cycle trigonometric functions.

[Bug fortran/86268] [9.0] Error on correct code with PDTs

2024-01-20 Thread ctechnodev at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86268

Alexander Westbrooks  changed:

   What|Removed |Added

 CC||ctechnodev at gmail dot com

--- Comment #3 from Alexander Westbrooks  ---
Created attachment 57178
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57178=edit
Proposed Patch to fix PR82943, PR86148, PR86268

[Bug fortran/86148] parameterized type compile time error

2024-01-20 Thread ctechnodev at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86148

Alexander Westbrooks  changed:

   What|Removed |Added

 CC||ctechnodev at gmail dot com

--- Comment #6 from Alexander Westbrooks  ---
Created attachment 57177
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57177=edit
Proposed Patch to fix PR82943, PR86148, PR86268

[Bug fortran/57360] Implement a warning for implied save

2024-01-20 Thread w6ws at earthlink dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57360

--- Comment #5 from Walter Spector  ---
IMHO this should be a "surprising" warning when -Wsurprising is specified.
  The message should suggest adding an explicit SAVE attribute to make the code
clear.

[Bug fortran/82943] [F03] Error with type-bound procedure of parametrized derived type

2024-01-20 Thread ctechnodev at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82943

--- Comment #15 from Alexander Westbrooks  ---
Created attachment 57176
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57176=edit
Proposed Patch to fix PR82943, PR86148, PR86268

[Bug c++/104094] Alias template shown in diagnostic with wrong template parameter name

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104094

--- Comment #3 from Andrew Pinski  ---
(In reply to Jonathan Wakely from comment #2)
> _Pattern is used in lazy_split_view, split_view and join_view, none of which
> are used at all by `ranges::to`. Is there some has collision going on here
> when the pretty printer finds names? Does it need an additional
> disambiguation step if more than one name is found?

Maybe that is PR 66968 (or PR 99) which I see are already linked here?

[Bug tree-optimization/113026] Bogus -Wstringop-overflow warning on simple memcpy type loop

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113026

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug c/113524] New: FAIL: gcc.dg/torture/pr113026-1.c -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (test for bogus messages, line 10)

2024-01-20 Thread danglin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113524

Bug ID: 113524
   Summary: FAIL: gcc.dg/torture/pr113026-1.c   -O3
-fomit-frame-pointer -funroll-loops -fpeel-loops
-ftracer -finline-functions   (test for bogus
messages, line 10)
   Product: gcc
   Version: 14.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c
  Assignee: unassigned at gcc dot gnu.org
  Reporter: danglin at gcc dot gnu.org
  Target Milestone: ---
  Host: hppa*-*-linux*
Target: hppa*-*-linux*
 Build: hppa*-*-linux*

spawn -ignore SIGHUP /home/dave/gnu/gcc/objdir/gcc/xgcc
-B/home/dave/gnu/gcc/obj
dir/gcc/ /home/dave/gnu/gcc/gcc/gcc/testsuite/gcc.dg/torture/pr113026-1.c
-fdiag
nostics-plain-output -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops
-ftracer -finline-functions -Wall -S -o pr113026-1.s
/home/dave/gnu/gcc/gcc/gcc/testsuite/gcc.dg/torture/pr113026-1.c: In function
'foo':
/home/dave/gnu/gcc/gcc/gcc/testsuite/gcc.dg/torture/pr113026-1.c:10:12:
warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
/home/dave/gnu/gcc/gcc/gcc/testsuite/gcc.dg/torture/pr113026-1.c:4:6: note: at
offset 16 into destination object 'dst' of size 16
FAIL: gcc.dg/torture/pr113026-1.c   -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions   (test for bogus messages, line 10)
PASS: gcc.dg/torture/pr113026-1.c   -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions  (test for excess errors)

Only occurs at -O3.

[Bug c/111693] -Wuse-after-free is documented in the wrong location

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111693

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug target/112804] ICE in aarch64 crosscompiler in plus_constant, at explow.cc:102 with -mabi=ilp32 and -finline-stringops

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112804

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug tree-optimization/112734] ICE verify_gimple failed since r14-3751-g8c984a1c3693df - BitInt

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112734

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug target/110265] RISC-V: ICE when build RVV intrinsic integer reduction with "-march=rv32gc_zve64d -mabi=ilp32d", both GCC 14 and 13.

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110265

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug other/110205] Some new warnings from clang for the range code

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110205

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug target/109811] libjxl 0.7 is a lot slower in GCC 13.1 vs Clang 16

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109811

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug c/110029] more precise documentation for cleanup attribute

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110029

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug target/109615] Redundant VSETVL after optimized code of RVV

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109615

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug target/109253] libbpf: failed to find BTF info for global/extern symbol '__divdi3'

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109253

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug target/108640] ICE compiling busybox for m68k in change_address_1, at emit-rtl.cc:2283

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108640

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug target/108521] gcc/doc/invoke.texi contains remnants of Cygwin options removed in 2010-10-07

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108521

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug ipa/108470] Missing documentation for alternate uses of __attribute__((noinline))

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108470

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug tree-optimization/107839] spurious "may be used uninitialized" warning while all uses are under "if (c)"

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107839

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |12.3

[Bug testsuite/106682] Powerpc test gcc.target/powerpc/pr86731-fwrapv-longlong.c fails on power8, passes on power9/power10

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106682

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |13.0

[Bug testsuite/106516] New test case gcc.dg/pr104992.c fails on power 10

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106516

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |13.0

[Bug analyzer/106229] False positives from -Wanalyzer-tainted-array-index with unsigned char index

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106229

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0
   Keywords||diagnostic

[Bug rtl-optimization/106187] armhf: Miscompilation at O2 level (O0 / O1 are working)

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106187

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |11.4

[Bug analyzer/106147] RFE: -fanalyzer could complain about some cases of infinite loops and infinite recursion

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106147

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0
   Keywords||diagnostic

[Bug target/105525] some targets don't define __INTPTR_TYPE__ breaking libgcov-driver.c

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105525

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug target/104401] [x86] Failure to recognize min/max pattern using pcmp+pblendv

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104401

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug c/102998] Wrong documentation for -Warray-parameter

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102998

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug middle-end/104355] Misleading -Warray-bounds documentation says "always out of bounds"

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104355

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |12.0

[Bug target/99888] Add powerpc ELFv2 support for -fpatchable-function-entry*

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99888

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |13.0

[Bug c++/99701] std::nullptr_t can be compared with relational ops

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99701

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |12.0

[Bug rtl-optimization/96388] scheduling takes forever with -fPIC

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96388

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug target/96176] Failure to omit extraneous movzx in atomic compare exchange with unsigned char

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96176

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |11.0

[Bug tree-optimization/95424] Failure to optimize division with numerator of 1

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95424

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |12.0

[Bug other/94629] 10 issues located by the PVS-studio static analyzer

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94629

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug testsuite/94253] FAIL: gfortran.dg/bind_c_coms.f90 -O0 (test for excess errors)

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94253

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug tree-optimization/86724] Compilation error with new isl 0.20 (missing includes)

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86724

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |7.4

[Bug debug/84645] -flto -g0 at compile-time vs. -flto -g at link time ICEs in add_dwarf_attr, at dwarf2out.c:4353

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84645

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |8.0

[Bug c++/87699] Implement CWG 1512

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87699

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |11.0

[Bug tree-optimization/113463] ICE: in extended_tree, at tree.h:6449 with _BitInt() used as offset

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113463

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug tree-optimization/113102] during GIMPLE pass: bitintlower ICE: SIGSEGV with _BitInt() at -O1 or -O2

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113102

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug target/30271] -mstrict-align can add an store extra for struct argument passing

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30271

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug tree-optimization/112941] during GIMPLE pass: bitintlower ICE: in handle_operand_addr, at gimple-lower-bitint.cc:2126 (gimple-lower-bitint.cc:2134) at -O with _BitInt()

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112941

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug tree-optimization/113491] ICE: SIGSEGV in make_ssa_name_fn (tree-ssanames.cc:354) at -Os with _BitInt() used as switch control expression

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113491

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug tree-optimization/113462] ICE: in handle_cast, at gimple-lower-bitint.cc:1539 at -O with _BitInt() in a struct

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113462

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug tree-optimization/113464] ICE: in lower_asm, at gimple-lower-bitint.cc:5200 with invalid __asm__ on _BitInt() at -O1 and above

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113464

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug tree-optimization/113421] wrong code with -O -fno-tree-fre and _BitInt() multiplication

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113421

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug middle-end/113410] ICE: in maybe_check_access_sizes, at gimple-ssa-warn-access.cc:3423 with _BitInt() used as array length

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113410

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug middle-end/113409] ICE: in omp_extract_for_data, at omp-general.cc:411 with -fopenmp-simd and _BitInt()

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113409

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug tree-optimization/113408] ICE: in handle_cast, at gimple-lower-bitint.cc:1539 at -O with _BitInt()

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113408

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug middle-end/113406] ICE: tree check: expected class 'type', have 'exceptional' (error_mark) in useless_type_conversion_p, at gimple-expr.cc:85 with -fstrub=internal and _BitInt() (and __GIMPLE wit

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113406

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug tree-optimization/113372] wrong code with _BitInt() arithmetics at -O1

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113372

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug target/113393] RISC-V: Full coverage test bugs for upstream 20240112

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113393

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug tree-optimization/113361] wrong code with __builtin_mul_overflow_p() and _BitInt() at -O0

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113361

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug c++/113389] ICE when explicit object parameter is not declared as the first parameter

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113389

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug tree-optimization/113330] ICE: verify_gimple failed: conversion of register to a different size in 'view_convert_expr' with -O -fstack-check=generic and _BitInt()

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113330

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug target/113324] internal compiler error: in reload_combine_note_use, at postreload.c:1534

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113324

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |11.0

[Bug tree-optimization/113323] ICE: tree check: expected none of vector_type, have vector_type in bitint_precision_kind, at gimple-lower-bitint.cc:131 with _BitInt()

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113323

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug tree-optimization/113316] during GIMPLE pass: bitintlower ICE: SIGSEGV in var_to_partition (tree-ssa-live.h:163) at -O with uninitialized _BitInt() function argument

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113316

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug c/113315] during GIMPLE pass: bitintlower0 ICE: in lower_mergeable_stmt, at gimple-lower-bitint.cc:2310 with _BitInt() used as array index

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113315

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug tree-optimization/113459] ICE: in as_a, at machmode.h:381 with memset() on a _BitInt() at -O1 and above

2024-01-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113459

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |14.0

[Bug c/102998] Wrong documentation for -Warray-parameter

2024-01-20 Thread sandra at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102998

sandra at gcc dot gnu.org changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #6 from sandra at gcc dot gnu.org ---
Fixed.

[Bug fortran/111291] ASAN error: heap-use-after-free gcc/fortran/parse.cc:359 in decode_statement

2024-01-20 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111291

--- Comment #5 from GCC Commits  ---
The master branch has been updated by Mikael Morin :

https://gcc.gnu.org/g:6930e1f1055c39bea170c25f694f7301989e5d1d

commit r14-8305-g6930e1f1055c39bea170c25f694f7301989e5d1d
Author: Mikael Morin 
Date:   Fri Jan 19 18:47:36 2024 +0100

fortran: Restore current interface info on error [PR111291]

This change is a followup to the fix for PR48776 (namely
r14-3572-gd58150452976c4ca65ddc811fac78ef956fa96b0 AKA
fortran: Restore interface to its previous state on error [PR48776]),
which cleaned up new changes from interfaces upon error.

Unfortunately, there is one case in that fix that is mishandled, visible
on unexpected_interface.f90 with valgrind or an asan-instrumented gfortran.
when an interface statement is found while parsing an interface body (which
is invalid), the current interface is replaced by the one from the new
statement, and as parsing continues, new procedures are added
to the new interface, which has been rejected and freed, instead of the
original one.

This change restores the current interface pointer to its previous value
on each rejected statement.

PR fortran/48776
PR fortran/111291

gcc/fortran/ChangeLog:

* parse.cc: Restore current interface to its previous value on
error.

[Bug fortran/48776] ICE(segfault) after -std=f95 diagnostic error involving PROCEDURE

2024-01-20 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48776

--- Comment #12 from GCC Commits  ---
The master branch has been updated by Mikael Morin :

https://gcc.gnu.org/g:6930e1f1055c39bea170c25f694f7301989e5d1d

commit r14-8305-g6930e1f1055c39bea170c25f694f7301989e5d1d
Author: Mikael Morin 
Date:   Fri Jan 19 18:47:36 2024 +0100

fortran: Restore current interface info on error [PR111291]

This change is a followup to the fix for PR48776 (namely
r14-3572-gd58150452976c4ca65ddc811fac78ef956fa96b0 AKA
fortran: Restore interface to its previous state on error [PR48776]),
which cleaned up new changes from interfaces upon error.

Unfortunately, there is one case in that fix that is mishandled, visible
on unexpected_interface.f90 with valgrind or an asan-instrumented gfortran.
when an interface statement is found while parsing an interface body (which
is invalid), the current interface is replaced by the one from the new
statement, and as parsing continues, new procedures are added
to the new interface, which has been rejected and freed, instead of the
original one.

This change restores the current interface pointer to its previous value
on each rejected statement.

PR fortran/48776
PR fortran/111291

gcc/fortran/ChangeLog:

* parse.cc: Restore current interface to its previous value on
error.

[Bug c/113438] ICE (segfault) in dwarf2out_decl with -g -std=c23 on c23-tag-composite-2.c

2024-01-20 Thread uecker at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113438

uecker at gcc dot gnu.org changed:

   What|Removed |Added

 Target|aarch64-*-* |

--- Comment #3 from uecker at gcc dot gnu.org ---
Not aarch64 specific.

[Bug c/113492] ICE: in composite_type_internal, at c/c-typeck.cc:557 with -std=c2x -funsigned-bitfields since r14-6808

2024-01-20 Thread uecker at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113492

--- Comment #11 from uecker at gcc dot gnu.org ---
Created attachment 57175
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57175=edit
patch


Untested patch.

  1   2   >