[Bug libgcc/71744] Concurrently throwing exceptions is not scalable

2023-01-08 Thread fw at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71744 Florian Weimer changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug target/108338] New: use mtvsrws for lowpart DI->SF conversion on P9

2023-01-08 Thread guojiufu at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108338 Bug ID: 108338 Summary: use mtvsrws for lowpart DI->SF conversion on P9 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug target/103743] PPC: Inefficient equality compare for large 64-bit constants having only 16-bit relevant bits in high part

2023-01-08 Thread guojiufu at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103743 Jiu Fu Guo changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug tree-optimization/107409] Perf loss ~5% on 519.lbm_r SPEC cpu2017 benchmark with r10-5090-ga9a4edf0e71bba

2023-01-08 Thread rvmallad at amazon dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107409 --- Comment #15 from Rama Malladi --- Hi, Can we review this issue and suggest next steps/ action please? Thanks.

[Bug modula2/108182] gm2 driver mishandles target and multilib options

2023-01-08 Thread gaius at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108182 --- Comment #9 from Gaius Mulley --- Created attachment 54214 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54214=edit Potential fix for target multilib_dir handling -m and -f (version 3) version3 work in progress, implemented using

[Bug libfortran/108336] Repeatable random_numbers with openmp

2023-01-08 Thread gareth.davies.ga.code at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108336 --- Comment #6 from Gareth Davies --- (In reply to anlauf from comment #4) > There is one flaw with the testcase: when OMP_NUM_THREADS > n1, > array elements threadval(n1+1:OMP_NUM_THREADS) are filled with > undefined values. Yes, my bad in

[Bug libstdc++/77691] [10/11/12/13 regression] experimental/memory_resource/resource_adaptor.cc FAILs

2023-01-08 Thread danglin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77691 --- Comment #54 from John David Anglin --- Created attachment 54213 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54213=edit Patch to fix test failure on hppa64-hp-hpux11.11

[Bug libfortran/108336] Repeatable random_numbers with openmp

2023-01-08 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108336 --- Comment #5 from Andrew Pinski --- Maybe instead of: !$omp parallel nt = omp_get_num_threads() !$omp end parallel Do: nt = omp_get_max_threads() that should improve the situtation of not allocating enough for the array.

[Bug target/108337] Misaligned memory access issues when inline assembly is used with optimization on x86_64

2023-01-08 Thread eric-bugs at omnifarious dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108337 --- Comment #5 from eric-bugs at omnifarious dot org --- (In reply to Andrew Pinski from comment #4) > Yes it affects every function. There might be another way to use attribute > to specific that only main needs this treatment. Or better yet

[Bug target/108337] Misaligned memory access issues when inline assembly is used with optimization on x86_64

2023-01-08 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108337 Andrew Pinski changed: What|Removed |Added Resolution|FIXED |INVALID --- Comment #4 from Andrew

[Bug target/108337] Misaligned memory access issues when inline assembly is used with optimization on x86_64

2023-01-08 Thread eric-bugs at omnifarious dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108337 eric-bugs at omnifarious dot org changed: What|Removed |Added Resolution|INVALID |FIXED --- Comment #3

[Bug fortran/108131] [10/11 Regression] Incorrect bound calculation when bound intrinsic used in size expression

2023-01-08 Thread anlauf at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108131 anlauf at gcc dot gnu.org changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[Bug libfortran/108336] Repeatable random_numbers with openmp

2023-01-08 Thread anlauf at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108336 --- Comment #4 from anlauf at gcc dot gnu.org --- There is one flaw with the testcase: when OMP_NUM_THREADS > n1, array elements threadval(n1+1:OMP_NUM_THREADS) are filled with undefined values. When I replace the line

[Bug fortran/108131] [10/11 Regression] Incorrect bound calculation when bound intrinsic used in size expression

2023-01-08 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108131 --- Comment #8 from CVS Commits --- The releases/gcc-10 branch has been updated by Harald Anlauf : https://gcc.gnu.org/g:ba5012875bc6f7910be3b5cce03e000aa9322c1f commit r10-11155-gba5012875bc6f7910be3b5cce03e000aa9322c1f Author: Harald Anlauf

[Bug fortran/108131] [10/11 Regression] Incorrect bound calculation when bound intrinsic used in size expression

2023-01-08 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108131 --- Comment #7 from CVS Commits --- The releases/gcc-11 branch has been updated by Harald Anlauf : https://gcc.gnu.org/g:04310741924e7e6ef1ec637a1a9c3e2972345926 commit r11-10458-g04310741924e7e6ef1ec637a1a9c3e2972345926 Author: Harald Anlauf

[Bug libstdc++/108228] /usr/lib/pa20_64/dld.sl: Unsatisfied code symbol '_ZN9__gnu_cxx21zoneinfo_dir_ov errideEv'

2023-01-08 Thread danglin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108228 John David Anglin changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug libstdc++/108235] FAIL: g++.dg/compat/abi/bitfield1 cp_compat_x_tst.o-cp_compat_y_tst.o link

2023-01-08 Thread danglin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108235 John David Anglin changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug target/108004] x-form logical operations with dot instructions are not emitted.

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

[Bug target/108337] Misaligned memory access issues when inline assembly is used with optimization on x86_64

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

[Bug target/108337] Misaligned memory access issues when inline assembly is used with optimization on x86_64

2023-01-08 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108337 --- Comment #1 from Andrew Pinski --- It might be the case the stack pointer is not inlined when main is called from the kernel ... What target is this? X86_64-linux-gnu?

[Bug c++/108337] New: Misaligned memory access issues when inline assembly is used with optimization on x86_64

2023-01-08 Thread eric-bugs at omnifarious dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108337 Bug ID: 108337 Summary: Misaligned memory access issues when inline assembly is used with optimization on x86_64 Product: gcc Version: 12.2.1 Status: UNCONFIRMED

[Bug rtl-optimization/107949] PPC: Unnecessary rlwinm after lbzx

2023-01-08 Thread segher at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107949 Segher Boessenkool changed: What|Removed |Added CC||segher at gcc dot gnu.org ---

[Bug target/108004] x-form logical operations with dot instructions are not emitted.

2023-01-08 Thread segher at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108004 Segher Boessenkool changed: What|Removed |Added CC||segher at gcc dot gnu.org ---

[Bug middle-end/108300] `abort()` macro cause bootstrap failure on *-w64-mingw32

2023-01-08 Thread i.nixman at autistici dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108300 --- Comment #13 from niXman --- could it be because now as host toolchain used a version which contains the changes LIU Hao is talked about?

[Bug tree-optimization/106238] Inline optimization causes dangling pointer on "include/c++/12.1.0/bits/stl_tree.h"

2023-01-08 Thread romain.geissler at amadeus dot com via Gcc-bugs
--- Comment #5 from Romain Geissler --- Hi, This seems to still happen with current trunk: #include std::map _Map; void f() { std::map localMap; _Map.swap(localMap); } compiled with -Wall -Werror -O2: In file included from /opt/compiler-explorer/gcc-trunk-20230108/include/c++/13.0.0

[Bug middle-end/108300] `abort()` macro cause bootstrap failure on *-w64-mingw32

2023-01-08 Thread i.nixman at autistici dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108300 --- Comment #12 from niXman --- guys, does anyone have an idea why I faced with the error on gcc-12.2.0 ? ``` ../../../../src/gcc-12.2.0/libcpp/system.h:404:30: error: expected identifier before string constant 404 | #define abort()

[Bug libstdc++/108221] Building cross compiler for H8 family fails at libstdc++-v3/src/c++20/tzdb.cc

2023-01-08 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108221 --- Comment #13 from Jan Dubiec --- FYI, Jonathan. This time the target is msp430-elf. Making all in c++20 make[9]: Entering directory '/d/Works/xcomp/gcc-build/msp430-elf/large/libstdc++-v3/src/c++20' /bin/sh ../../libtool --tag CXX --tag

[Bug tree-optimization/108334] Strange message in libgav1

2023-01-08 Thread lukaszcz18 at wp dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108334 --- Comment #3 from Jamaika --- I add preprocessed source `cdef.o`.

[Bug libfortran/108336] Repeatable random_numbers with openmp

2023-01-08 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108336 --- Comment #3 from Andrew Pinski --- Yes the race condition is the following: the order of calling random_number on which thread first. init_rand_state definitely takes a lock when reading/writing from/to master_state. I see no other race

[Bug tree-optimization/108334] Strange message in libgav1

2023-01-08 Thread lukaszcz18 at wp dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108334 --- Comment #2 from Jamaika --- Created attachment 54212 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54212=edit preprocessed source

[Bug libstdc++/108326] Question about definitions in c++config.h for gcc13 20221229

2023-01-08 Thread lukaszcz18 at wp dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108326 --- Comment #4 from Jamaika --- Here was my mistake. I tried adding c++config definitions to gcc 11.3.1 with _GLIBCXX_HAS_GTHREADS. Unfortunately many more features are changed to native Windows.

[Bug fortran/108336] Repeatable random_numbers with openmp

2023-01-08 Thread gareth.davies.ga.code at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108336 --- Comment #2 from Gareth Davies --- (In reply to Andrew Pinski from comment #1) > Most likely there is only one seed per program so the random # generator is > using locks. So the order is dependent on which thread calls the function. > >

[Bug driver/108328] gcc --help -v doesn't work correctly in some circumstances in gcc>=10

2023-01-08 Thread sagimor6 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108328 --- Comment #7 from Sagi Mor --- Ok, now I understand what you said about the kernel and sysroot. Yes, it is weird. (non buildroot kernel compiled with 64k pages, buildroot sysroot with 4k max).

[Bug target/106704] [12/13 Regression] avx intrinsic not generating vblendvps instruction with -mavx

2023-01-08 Thread roger at nextmovesoftware dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106704 Roger Sayle changed: What|Removed |Added CC||roger at nextmovesoftware dot com

[Bug fortran/108336] Repeatable random_numbers with openmp

2023-01-08 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108336 --- Comment #1 from Andrew Pinski --- Most likely there is only one seed per program so the random # generator is using locks. So the order is dependent on which thread calls the function. Now having a seed per thread might be a good idea but

[Bug driver/108328] gcc --help -v doesn't work correctly in some circumstances in gcc>=10

2023-01-08 Thread sagimor6 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108328 --- Comment #6 from Sagi Mor --- Well, this is only for aarch64 and arc, and they do compile the kernel in buildroot, so it seems to work? (never checked myself) By the way, they solve the -Wl,z,relro for kernel/uboot compilation by checking if

[Bug fortran/108336] New: Repeatable random_numbers with openmp

2023-01-08 Thread gareth.davies.ga.code at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108336 Bug ID: 108336 Summary: Repeatable random_numbers with openmp Product: gcc Version: 11.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran

[Bug c++/108335] New: New-expression doesn't perform mandatory copy elision when copy constructor is disabled with `requires`, in a template

2023-01-08 Thread iamsupermouse at mail dot ru via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108335 Bug ID: 108335 Summary: New-expression doesn't perform mandatory copy elision when copy constructor is disabled with `requires`, in a template Product: gcc

[Bug tree-optimization/108334] Strange message in libgav1

2023-01-08 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108334 --- Comment #1 from Andrew Pinski --- Can you attach the preprocessed source? GCC thinks you are trying to do a memcpy to a null pointer really: cc1plus.exe: note: destination object is likely at address zero Which could mean either the code