[Bug libfortran/109662] bad namelist input but gfortran accepted it

2023-04-30 Thread jvdelisle at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109662 --- Comment #4 from Jerry DeLisle --- I knew this looked familiar. We did it on purpose. From list_read.c: /* A trailing space is required, we give a little latitude here, 10.9.1. */ c = next_char (dtp); if (!is_separator(c) && c != '!

[Bug c++/109671] Spurious dangling reference warning in GCC 13

2023-04-30 Thread lopresti at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109671 --- Comment #3 from Patrick J. LoPresti --- (In reply to Andrew Pinski from comment #1) > There is no way for GCC to know that get_foo_by_name does not store the > argument into what is returned so it warns about this case ... To summarize: GC

[Bug libfortran/109662] bad namelist input but gfortran accepted it

2023-04-30 Thread jvdelisle at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109662 Jerry DeLisle changed: What|Removed |Added CC||jvdelisle at gcc dot gnu.org

[Bug fortran/109641] Gfortran fails to overload intrinsic operator (*) if operands are complex. It works with real ones.

2023-04-30 Thread adelson.oliveira at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109641 --- Comment #14 from Adelson Oliveira --- Ok, thanks. Em sáb., 29 de abr. de 2023 11:55 PM, escreveu: > Attachments with a MIME type of "text/html" are not allowed on this > installation. > > Adelson Oliveira wrote: > > Thanks, anlauf > > > >

[Bug libfortran/109662] bad namelist input but gfortran accepted it

2023-04-30 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109662 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org ---

[Bug c/107926] wrong error message for excess elements in array initializer using a string literal

2023-04-30 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107926 Andrew Pinski changed: What|Removed |Added Resolution|--- |FIXED Target Milestone|---

[Bug c/107926] wrong error message for excess elements in array initializer using a string literal

2023-04-30 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107926 --- Comment #4 from CVS Commits --- The trunk branch has been updated by Andrew Pinski : https://gcc.gnu.org/g:a6b810ae783acf8cec2d2272a46bd6de0976f496 commit r14-363-ga6b810ae783acf8cec2d2272a46bd6de0976f496 Author: Andrew Pinski Date: Wed

[Bug c++/109682] coroutines: ICE in morph_fn_to_coro on wrong return type for get_return_object_on_allocation_failure

2023-04-30 Thread dv at vollmann dot ch via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109682 dv at vollmann dot ch changed: What|Removed |Added CC||dv at vollmann dot ch --- Commen

[Bug c++/109682] New: coroutines: ICE in morph_fn_to_coro on wrong return type for get_return_object_on_allocation_failure

2023-04-30 Thread dv at vollmann dot ch via Gcc-bugs
0xb70e4a c_parse_file() /build/src/gcc/gcc/cp/parser.cc:49627 0xcaf411 c_common_parse_file() /build/src/gcc/gcc/c-family/c-opts.cc:1248 Version: GNU C++23 (GCC) version 14.0.0 20230430 (experimental) (x86_64-pc-linux-gnu) Configured with: /build/src/gcc/configure --prefix=/opt/nat

[Bug analyzer/108171] [13/14 Regression] ICE in binding_key::make, at analyzer/store.cc:132 since r13-4529-gdfe2ef7f2b6cac70

2023-04-30 Thread arsen at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108171 Arsen Arsenović changed: What|Removed |Added CC||arsen at gcc dot gnu.org --- Comment

[Bug sanitizer/109674] [14 Regression] linking with libhwasan is now broken

2023-04-30 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109674 Martin Liška changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug sanitizer/109674] [14 Regression] linking with libhwasan is now broken

2023-04-30 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109674 --- Comment #6 from CVS Commits --- The master branch has been updated by Martin Liska : https://gcc.gnu.org/g:54765c875a0ec961e06d56d916d9ad1ddfc3b221 commit r14-359-g54765c875a0ec961e06d56d916d9ad1ddfc3b221 Author: Martin Liska Date: Sun

[Bug sanitizer/109674] [14 Regression] linking with libhwasan is now broken

2023-04-30 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109674 --- Comment #5 from Martin Liška --- The solution is probably very similar to libasan library where also __lsan symbols are used and where we link against ../lsan/.libs/libsanitizer_lsan.a.

[Bug sanitizer/109674] [14 Regression] linking with libhwasan is now broken

2023-04-30 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109674 Martin Liška changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug sanitizer/109674] [14 Regression] linking with libhwasan is now broken

2023-04-30 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109674 --- Comment #3 from Andreas Schwab --- The __lsan symbols are defined in liblsan, but only as local symbols.

[Bug sanitizer/109674] [14 Regression] linking with libhwasan is now broken

2023-04-30 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109674 Andrew Pinski changed: What|Removed |Added Resolution|INVALID |--- Status|RESOLVED

[Bug sanitizer/109674] [14 Regression] linking with libhwasan is now broken

2023-04-30 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109674 Martin Liška changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug libstdc++/108030] `std::experimental::simd` not inlined

2023-04-30 Thread mkretz at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108030 Matthias Kretz (Vir) changed: What|Removed |Added Target Milestone|13.2|12.4 --- Comment #15 from Matthi

[Bug c++/101118] coroutines: unexpected ODR warning for coroutine frame type in LTO builds

2023-04-30 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101118 --- Comment #18 from CVS Commits --- The releases/gcc-12 branch has been updated by Iain D Sandoe : https://gcc.gnu.org/g:b7e75cdb218f25708b8b1aa3f4b138d88187491f commit r12-9501-gb7e75cdb218f25708b8b1aa3f4b138d88187491f Author: Iain Sandoe D

[Bug c++/107768] Bogus -Wzero-as-null-pointer-constant in coroutine

2023-04-30 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107768 --- Comment #10 from CVS Commits --- The releases/gcc-12 branch has been updated by Iain D Sandoe : https://gcc.gnu.org/g:db0985039fa58d5ef5d4ed10d2cbfd5b3ea6b3ee commit r12-9500-gdb0985039fa58d5ef5d4ed10d2cbfd5b3ea6b3ee Author: Andrew Pinski