[Bug driver/115368] Wrong order of gcc include paths on musl systems

2024-06-06 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115368 Khem Raj changed: What|Removed |Added Attachment #58366|0 |1 is obsolete|

[Bug driver/115368] Wrong order of gcc include paths on musl systems

2024-06-06 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115368 --- Comment #1 from Khem Raj --- Created attachment 58366 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58366=edit potential fix This patch uses -idirafter instead of -iprefix when building for musl. This fixes the issue as the search

[Bug driver/115368] New: Wrong order of gcc include paths on musl systems

2024-06-06 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115368 Bug ID: 115368 Summary: Wrong order of gcc include paths on musl systems Product: gcc Version: 14.1.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug target/115042] New: valgrind test fails to compile on armv7

2024-05-10 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115042 Bug ID: 115042 Summary: valgrind test fails to compile on armv7 Product: gcc Version: 14.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug target/113986] [14 regression] Build failure on aarch64-linux-musl or if ifunc support is disabled (error: 'export_load_16' aliased to undefined symbol 'libat_load_16')

2024-03-26 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113986 Khem Raj changed: What|Removed |Added CC||raj.khem at gmail dot com --- Comment #5

[Bug target/110061] libatomic: 128-bit atomics should be lock-free on AArch64

2024-03-17 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110061 Khem Raj changed: What|Removed |Added CC||raj.khem at gmail dot com --- Comment #17

[Bug target/110901] -march does not override -mcpu on aarch64

2023-08-04 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110901 --- Comment #2 from Khem Raj --- (In reply to Andrew Pinski from comment #1) > Order matters. In this case -march is after -mcpu ... It does not seem to be effective in this case. I tried to specify -mcpu after -march and vice-versa, result is

[Bug driver/110901] New: -march does not override -mcpu on aarch64

2023-08-04 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110901 Bug ID: 110901 Summary: -march does not override -mcpu on aarch64 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug c++/108681] New: gcc hangs compiling opencv/channels_combine.cpp for aarch64

2023-02-05 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108681 Bug ID: 108681 Summary: gcc hangs compiling opencv/channels_combine.cpp for aarch64 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal

[Bug tree-optimization/108647] [13 Regression] ICE in upper_bound, at value-range.h:950 with -O3 since r13-2974-g67166c9ec35d58ef

2023-02-03 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108647 --- Comment #22 from Khem Raj --- (In reply to Jakub Jelinek from comment #20) > How could these changes result in > ../harfbuzz-6.0.0/src/hb-map.hh:295:5: error: no match for ‘operator|’ > (operand types are ‘hb_filter_iter_t unsigned int,

[Bug c++/107461] [12 Regression] ambiguity error for friend with templated constexpr argument

2023-02-03 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107461 Khem Raj changed: What|Removed |Added CC||raj.khem at gmail dot com --- Comment #6

[Bug tree-optimization/108647] [13 Regression] ICE in upper_bound, at value-range.h:950 with -O3 since r13-2974-g67166c9ec35d58ef

2023-02-03 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108647 Khem Raj changed: What|Removed |Added CC||raj.khem at gmail dot com --- Comment #19

[Bug target/105144] [12 Regression] Bootstrap + install failure on aarch64 due to aarch64-tune.md likely since r12-7842

2023-01-31 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105144 --- Comment #10 from Khem Raj --- (In reply to Andrew Pinski from comment #9) > (In reply to Andrew Pinski from comment #8) > > (In reply to Khem Raj from comment #7) > > > in Yocto we build outside the source tree. And during cross-build it

[Bug target/105144] [12 Regression] Bootstrap + install failure on aarch64 due to aarch64-tune.md likely since r12-7842

2023-01-31 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105144 --- Comment #7 from Khem Raj --- in Yocto we build outside the source tree. And during cross-build it will copy aarch64.h into builddir and use it from there but then build can not find files it includes since its being included from builddir.

[Bug target/105144] [12 Regression] Bootstrap + install failure on aarch64 due to aarch64-tune.md likely since r12-7842

2023-01-31 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105144 Khem Raj changed: What|Removed |Added CC||raj.khem at gmail dot com --- Comment #6

[Bug c++/108564] New: RISCV std::atomic needs libatomics

2023-01-26 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108564 Bug ID: 108564 Summary: RISCV std::atomic needs libatomics Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug tree-optimization/105312] [11 Regression] ICE in gimple_expand_vec_cond_expr on arm-linux since r12-834-ga6eacbf1055520

2022-04-20 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105312 --- Comment #8 from Khem Raj --- yeah I can verify that the ICE is gone.

[Bug middle-end/105316] Seemingly bogus -Wdangling-pointer from ppc/ppc64 kernel printk with gcc12

2022-04-19 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105316 --- Comment #2 from Khem Raj --- ah yes. Thanks

[Bug middle-end/105316] New: Seemingly bogus -Wdangling-pointer from ppc/ppc64 kernel printk with gcc12

2022-04-19 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105316 Bug ID: 105316 Summary: Seemingly bogus -Wdangling-pointer from ppc/ppc64 kernel printk with gcc12 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity:

[Bug middle-end/105312] New: attribute__((optimize("-O3"))) stress_matrix_xy_identity compiling stress-ng for arm

2022-04-19 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105312 Bug ID: 105312 Summary: attribute__((optimize("-O3"))) stress_matrix_xy_identity compiling stress-ng for arm Product: gcc Version: 12.0 Status: UNCONFIRMED

[Bug target/105251] static assert sizeof(decltype(_together)) <= hardware_constructive_interference_size fails with gcc12

2022-04-14 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105251 --- Comment #11 from Khem Raj --- yes thanks. I have done so https://jira.mongodb.org/browse/SERVER-65664

[Bug target/105251] static assert sizeof(decltype(_together)) <= hardware_constructive_interference_size fails with gcc12

2022-04-14 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105251 --- Comment #9 from Khem Raj --- how does something like this look ? #include #include #include #include #ifdef __cpp_lib_hardware_interference_size using std::hardware_constructive_interference_size; using

[Bug target/105251] static assert sizeof(decltype(_together)) <= hardware_constructive_interference_size fails with gcc12

2022-04-14 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105251 --- Comment #8 from Khem Raj --- So in this case if I change static_assert(sizeof(decltype(_together)) <= hardware_constructive_interference_size, "cache line spill"); to static_assert(sizeof(decltype(_together))

[Bug target/105251] static assert sizeof(decltype(_together)) <= hardware_constructive_interference_size fails with gcc12

2022-04-13 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105251 --- Comment #6 from Khem Raj --- this is from mongodb.

[Bug target/105251] static assert sizeof(decltype(_together)) <= hardware_constructive_interference_size fails with gcc12

2022-04-13 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105251 --- Comment #4 from Khem Raj --- I dont think its a bug per-se, I am looking for fixing it right way. Should I pass a non-default value via gcc cmdline or adjust the size expectations in code.

[Bug middle-end/105253] __popcountdi2 calls generated in kernel code with gcc12

2022-04-12 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105253 --- Comment #3 from Khem Raj --- (In reply to Andrew Pinski from comment #1) > Two things. First the error message is for arm target but you then reference > x86_64 target options. > > Second there is a loop for popcount which gets translated

[Bug c/105253] New: __popcountdi2 calls generated in kernel code with gcc12

2022-04-12 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105253 Bug ID: 105253 Summary: __popcountdi2 calls generated in kernel code with gcc12 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal

[Bug c++/105251] New: static assert sizeof(decltype(_together)) <= hardware_constructive_interference_size fails with gcc12

2022-04-12 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105251 Bug ID: 105251 Summary: static assert sizeof(decltype(_together)) <= hardware_constructive_interference_size fails with gcc12 Product: gcc Version: 12.0

[Bug c++/105234] inlining failed in call to 'always_inline' 'memset': target specific option mismatch

2022-04-11 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105234 --- Comment #3 from Khem Raj --- Second sample works when I do not use _FORTIFY_SOURCES=2, so perhaps gcc-12 needs to adjust some glibc headers ?

[Bug c++/105234] inlining failed in call to 'always_inline' 'fmt::v8::basic_format_string::basic_format_string(const S&)

2022-04-11 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105234 --- Comment #2 from Khem Raj --- Created attachment 52787 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52787=edit test case 2

[Bug c++/105234] inlining failed in call to 'always_inline' 'fmt::v8::basic_format_string::basic_format_string(const S&)

2022-04-11 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105234 --- Comment #1 from Khem Raj --- here is another testcase from gnupg on mips with gcc12 failing $ mips-yoe-linux-gcc dirmngr.i In file included from

[Bug c++/105234] New: nlining failed in call to 'always_inline' 'fmt::v8::basic_format_string::basic_format_string(const S&)

2022-04-11 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105234 Bug ID: 105234 Summary: nlining failed in call to 'always_inline' 'fmt::v8::basic_format_string::basic_format_string(const S&) Product: gcc Version: 12.0 Status:

[Bug libstdc++/99453] libstdc++*-gdb.py installation depends on library naming

2021-05-26 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99453 Khem Raj changed: What|Removed |Added CC||raj.khem at gmail dot com --- Comment #8

[Bug analyzer/100011] internal compiler error in analyzer during IPA pass

2021-04-09 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100011 --- Comment #1 from Khem Raj --- this one seems to be the cause https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=3a66c289a3f395e50de79424e1e6f401a4dc1ab7

[Bug analyzer/100011] New: internal compiler error in analyzer during IPA pass

2021-04-09 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100011 Bug ID: 100011 Summary: internal compiler error in analyzer during IPA pass Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug target/99658] __divmoddi4 calls are generated on i686

2021-03-19 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99658 --- Comment #2 from Khem Raj --- (In reply to Richard Biener from comment #1) > Yes. GCC rightfully expects all libgcc functions to be available. Arguably > one divmod call is better than two calls to mod and div. thanks makes sense.

[Bug target/99658] New: __divmoddi4 calls are generated on i686

2021-03-19 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99658 Bug ID: 99658 Summary: __divmoddi4 calls are generated on i686 Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target

[Bug tree-optimization/99489] [11 Regression] internal compiler error: during GIMPLE pass: strlen in dlt_logstorage_log_file_name()

2021-03-13 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99489 --- Comment #10 from Khem Raj --- (In reply to Martin Sebor from comment #9) > Fixed in r11-7658. I validated the fix as well.

[Bug rtl-optimization/99581] New: internal compiler error: during RTL pass: final - void QTWTF::TCMalloc_PageHeap::scavengerThread()

2021-03-13 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99581 Bug ID: 99581 Summary: internal compiler error: during RTL pass: final - void QTWTF::TCMalloc_PageHeap::scavengerThread() Product: gcc Version: 11.0 Status: UNCONFIRMED

[Bug tree-optimization/99489] internal compiler error: during GIMPLE pass: strlen in dlt_logstorage_log_file_name()

2021-03-09 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99489 Khem Raj changed: What|Removed |Added Known to work||10.2.0 Host|

[Bug tree-optimization/99489] New: internal compiler error: during GIMPLE pass: strlen in dlt_logstorage_log_file_name()

2021-03-09 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99489 Bug ID: 99489 Summary: internal compiler error: during GIMPLE pass: strlen in dlt_logstorage_log_file_name() Product: gcc Version: 11.0 Status: UNCONFIRMED

[Bug target/99422] [11 Regression] ICE in extract_constrain_insn building glibc pthread_create

2021-03-08 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99422 --- Comment #16 from Khem Raj --- the kernel build failures still happen. I am re-opened #99454 and #99455

[Bug c/99455] internal compiler error: In function 'prb_reserve_in_last' in linux kernel

2021-03-08 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99455 --- Comment #3 from Khem Raj --- Created attachment 50333 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50333=edit testcase

[Bug c/99455] internal compiler error: In function 'prb_reserve_in_last' in linux kernel

2021-03-08 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99455 Khem Raj changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE

[Bug c/99454] internal compiler error: kernel module tg3 tg3_start_xmit

2021-03-08 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99454 Khem Raj changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED

[Bug target/99437] [11 Regression] Error: immediate value out of range 1 to 8 at operand 3 -- `shrn v1.8b,v1.8h,15'

2021-03-08 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99437 Khem Raj changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug c/99455] New: internal compiler error: In function 'prb_reserve_in_last' in linux kernel

2021-03-07 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99455 Bug ID: 99455 Summary: internal compiler error: In function 'prb_reserve_in_last' in linux kernel Product: gcc Version: 11.0 Status: UNCONFIRMED Severity:

[Bug c/99454] internal compiler error: kernel module tg3 tg3_start_xmit

2021-03-07 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99454 --- Comment #1 from Khem Raj --- btw. another data point when compiling with -Os it works but fails with -O1 or -O2 it was working ok with gcc snapshot from 10 days ago.

[Bug c/99454] New: internal compiler error: kernel module tg3 tg3_start_xmit

2021-03-07 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99454 Bug ID: 99454 Summary: internal compiler error: kernel module tg3 tg3_start_xmit Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal

[Bug target/99437] Error: immediate value out of range 1 to 8 at operand 3 -- `shrn v1.8b,v1.8h,15'

2021-03-06 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99437 --- Comment #1 from Khem Raj --- the version of gcc in use is gcc version 11.0.1 20210306 (experimental) (GCC)

[Bug target/99437] New: Error: immediate value out of range 1 to 8 at operand 3 -- `shrn v1.8b,v1.8h,15'

2021-03-06 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99437 Bug ID: 99437 Summary: Error: immediate value out of range 1 to 8 at operand 3 -- `shrn v1.8b,v1.8h,15' Product: gcc Version: 11.0 Status: UNCONFIRMED

[Bug c/99420] New: New warning -Warray-parameter

2021-03-05 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99420 Bug ID: 99420 Summary: New warning -Warray-parameter Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug c++/99354] New: spurious Wuninitialized warning diagnostic

2021-03-02 Thread raj.khem at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99354 Bug ID: 99354 Summary: spurious Wuninitialized warning diagnostic Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++