[Bug middle-end/110055] Dangling pointer warning inside std::vector on RISC-V

2023-06-05 Thread spriteovo at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110055 --- Comment #8 from Sprite --- (In reply to Richard Biener from comment #7) > The clobber is built by gimplify_target_expr and TARGET_EXPR_SLOT is changed > in place to the static variable. > > Does the following fix the RISC-V issue? > > diff

[Bug c++/110055] Dangling pointer warning inside std::vector on RISC-V

2023-05-31 Thread spriteovo at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110055 --- Comment #2 from Sprite --- Note that the error is raised only on the second and subsequent variables, the first variable works fine.

[Bug c++/110055] Dangling pointer warning inside std::vector on RISC-V

2023-05-31 Thread spriteovo at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110055 --- Comment #1 from Sprite --- $ g++ -v ``` Using built-in specs. COLLECT_GCC=g++ COLLECT_LTO_WRAPPER=/usr/lib/gcc/riscv64-unknown-linux-gnu/13.1.1/lto-wrapper Target: riscv64-unknown-linux-gnu Configured with: /build/gcc/src/gcc/configure --en

[Bug c++/110055] New: Dangling pointer warning inside std::vector on RISC-V

2023-05-31 Thread spriteovo at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110055 Bug ID: 110055 Summary: Dangling pointer warning inside std::vector on RISC-V Product: gcc Version: 13.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Com