[Bug target/118916] AARCH64: rtl-cse2 Option in O3 Level Optimization Ignores "volatile", Causing 'Invalid Instruction Syndrome'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118916 --- Comment #2 from Tomas Chang --- (In reply to Andrew Pinski from comment #1) > There is no ignoring volatile here since the exact memory locations are > written. > > Rather you have a memory location which needs to be written using an exact

[Bug target/118916] AARCH64: rtl-cse2 Option in O3 Level Optimization Ignores "volatile", Causing 'Invalid Instruction Syndrome'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118916 Tomas Chang changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INVALID

[Bug c/118916] New: AARCH64: rtl-cse2 Option in O3 Level Optimization Ignores "volatile", Causing 'Invalid Instruction Syndrome'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118916 Bug ID: 118916 Summary: AARCH64: rtl-cse2 Option in O3 Level Optimization Ignores "volatile", Causing 'Invalid Instruction Syndrome' Product: gcc Version: 14.2.1

[Bug tree-optimization/111154] vect-cost-model=dynamic triggers false warning on array operation

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54 --- Comment #3 from Tomas Chang --- (In reply to Richard Biener from comment #2) > Confirmed. Reproduces with -O3 -march=armv8.3-a and > > unsigned char desta[8]; > void copya(unsigned char *src, int size) > { > for (int i = 0; i < size; i++

[Bug c/111154] vect-cost-model=dynamic triggers false warning on array operation

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54 --- Comment #1 from Tomas Chang --- Forgot to mention, this bug can only be produced in 'AARCH64' platform. Native compile the attached test case in "aarch64" machine, or cross-compile the source code using aarch64 toolchain, can trigger it.

[Bug c/111154] New: vect-cost-model=dynamic triggers false warning on array operation

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54 Bug ID: 54 Summary: vect-cost-model=dynamic triggers false warning on array operation Product: gcc Version: 13.2.1 Status: UNCONFIRMED Severity: normal

[Bug tree-optimization/102124] [11/12 Regression] -ftree-loop-vectorize Causing Data To Lose Sign Bit on AARCH64 Platform

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102124 --- Comment #7 from Tomas Chang --- (In reply to Jakub Jelinek from comment #6) > Created attachment 51377 [details] > gcc12-pr102124.patch > > Untested fix. After applying this patch on GCC 11.2.1 code base, I re-built GCC on my AARCH64 box (

[Bug target/102124] [11/12 Regression] -ftree-loop-vectorize Causing Data To Lose Sign Bit on AARCH64 Platform

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102124 --- Comment #4 from Tomas Chang --- (In reply to Jakub Jelinek from comment #3) > Before vectorization the loop body is: > _1 = a_19(D) + i_29; > _2 = *_1; > _3 = (int) _2; > _4 = b_20(D) + i_29; > _5 = *_4; > _6 = (int) _5; > _7 =

[Bug c/102124] GCC 11.2.1 -ftree-loop-vectorize Causing Data To Lose Sign Bit

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102124 --- Comment #1 from Tomas Chang --- Test Program is as below: #include #include #include typedef uint8_t byte; int buf_eq_const(const void *_a, const void *_b, size_t len) { const byte *a = _a; const byte *b = _b; int ab, ba;

[Bug c/102124] New: GCC 11.2.1 -ftree-loop-vectorize Causing Data To Lose Sign Bit

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102124 Bug ID: 102124 Summary: GCC 11.2.1 -ftree-loop-vectorize Causing Data To Lose Sign Bit Product: gcc Version: 11.2.1 Status: UNCONFIRMED Severity: normal