https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119547
--- Comment #19 from GCC Commits ---
The releases/gcc-14 branch has been updated by Kito Cheng :
https://gcc.gnu.org/g:ae6ce4cd33d00b8acc9503b0d4883fa92c1a696d
commit r14-11700-gae6ce4cd33d00b8acc9503b0d4883fa92c1a696d
Author: Robin Dapp
Date
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119547
Robin Dapp changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119547
--- Comment #17 from GCC Commits ---
The master branch has been updated by Robin Dapp :
https://gcc.gnu.org/g:517f7e3f02b4c945d2b4bdabb490961cf986391e
commit r15-9491-g517f7e3f02b4c945d2b4bdabb490961cf986391e
Author: Robin Dapp
Date: Fri Ap
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119547
--- Comment #16 from Robin Dapp ---
> Yes, it is precisely the issue I have encountered in cvtScale8s64f (actually
> in cvt_64f). After the commit 34ae3a99, the default value of
> LOGICAL_OP_NON_SHORT_CIRCUIT has changed from 0 into 1, it will c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119547
--- Comment #15 from Robin Dapp ---
> Yes, it is precisely the issue I have encountered in cvtScale8s64f (actually
> in cvt_64f). After the commit 34ae3a99, the default value of
> LOGICAL_OP_NON_SHORT_CIRCUIT has changed from 0 into 1, it will c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119547
--- Comment #14 from 曾治金 ---
(In reply to Robin Dapp from comment #13)
> Hmm, now I compiled with -O3 on top of --param
> logical-op-non-short-circuit=0 (which shouldn't actually be necessary or
> change anything as it's the default) but there
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119547
--- Comment #13 from Robin Dapp ---
Hmm, now I compiled with -O3 on top of --param logical-op-non-short-circuit=0
(which shouldn't actually be necessary or change anything as it's the default)
but there is a segmentation fault in
_ZN2cv12cpu_b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119547
--- Comment #12 from Robin Dapp ---
> I recompile the opencv application with current gcc(commit b6aafe9a5b), and
> it still reproduce this bug. Do you have apply the patch of step 3 which
> enable vector implement of cvt_64f function?
Yes, I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119547
--- Comment #11 from 曾治金 ---
(In reply to Robin Dapp from comment #10)
> > 4. run
> > ```
> > export LD_LIBRARY_PATH=//lib
> > ./opencv_test_core
> > --gtest_filter="Core_ConvertScale/ElemWiseTest.accuracy/0"
> > ```
>
> [==] Runni
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119547
--- Comment #10 from Robin Dapp ---
> 4. run
> ```
> export LD_LIBRARY_PATH=//lib
> ./opencv_test_core --gtest_filter="Core_ConvertScale/ElemWiseTest.accuracy/0"
> ```
[==] Running 1 test from 1 test case.
[--] Global test e
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119547
--- Comment #9 from Robin Dapp ---
> cmake --build cross-build/$BUILD_DIR-gcc --target opencv_test_core -j10
> ```
> 4. run
> ```
> export LD_LIBRARY_PATH=//lib
> ./opencv_test_core --gtest_filter="Core_ConvertScale/ElemWiseTest.accuracy/0"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119547
--- Comment #6 from 曾治金 ---
This issue report in https://github.com/opencv/opencv/issues/26936, and I
extract it into my test case. I just check the assemble code and don't run the
test case.
But if you need to run the opencv application to fi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119547
--- Comment #8 from 曾治金 ---
This is my temporary patch and may be it's incorrect. Perhaps I am unable to
solve this issue, but I would like to offer this patch as a reference.
>From 2068f7493da45d67699de587224510659fe776a7 Mon Sep 17 00:00:00
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119547
--- Comment #7 from 曾治金 ---
(In reply to Li Pan from comment #2)
> Any information about gcc version? Seems asm layout is different from
> today's upstream. CC RISC-V relatives.
>
> 123 │ .L41:
> 124 │ addiw t2,t2,1
> 125 │ v
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119547
--- Comment #3 from 曾治金 ---
Hi, it will reproduce by gcc 14.2. And in gcc upstream code, you need to add
`--param logical-op-non-short-circuit=0` flag to reproduce. This is because the
default value of LOGICAL_OP_NON_SHORT_CIRCUIT of risc-v is c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119547
--- Comment #5 from Robin Dapp ---
Do you happen to have an excution test ready so I can have a look?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119547
曾治金 changed:
What|Removed |Added
CC||zhijin.zeng at spacemit dot com
--- Comment #4 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119547
Li Pan changed:
What|Removed |Added
CC||jeffreyalaw at gmail dot com,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119547
--- Comment #1 from 曾治金 ---
I think this issue has nothing to do with the logical-op-non-short-circuit
parameter and it is a bug of risc-v vsetvl pass. The risc-v vsetvl pass use lcm
algorithm to find the suitable place to insert vsetvl instruct
19 matches
Mail list logo
