https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115789
--- Comment #12 from Jeffrey A. Law ---
My suggestion is to wait for the LLVM release, then backport whatever we need
to be compatible with LLVM.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115789
--- Comment #10 from lu_zero at gentoo dot org ---
Passing `-mstrict-align` to gcc-14 to build gcc-14 does not seem to have
effect, same Bus error triggered.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115789
--- Comment #11 from Xi Ruoyao ---
(In reply to lu_zero from comment #10)
> Passing `-mstrict-align` to gcc-14 to build gcc-14 does not seem to have
> effect, same Bus error triggered.
Then it's a different bug. As Craig said -march=rv64gcv_zv
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115789
--- Comment #9 from Xi Ruoyao ---
(In reply to lu_zero from comment #8)
> (In reply to Xi Ruoyao from comment #4)
> > Should we backport -mvector-strict-align to release branches then? Arguably
> > this is not a bug fix (for the compiler) but x
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115789
--- Comment #8 from lu_zero at gentoo dot org ---
(In reply to Xi Ruoyao from comment #4)
> Should we backport -mvector-strict-align to release branches then? Arguably
> this is not a bug fix (for the compiler) but x86 (and maybe others) also
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115789
--- Comment #7 from lu_zero at gentoo dot org ---
(In reply to Jeffrey A. Law from comment #3)
> Thanks. Unfortunately GDB isn't dumping the vector regs, but I can make a
> pretty good guess that this is an unaligned memory access.
>
> => 0x000
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115789
--- Comment #6 from Xi Ruoyao ---
(In reply to Craig Topper from comment #5)
> Isn’t -mstrict-align the default? It is in LLVM.
Then it may be a different issue...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115789
--- Comment #5 from Craig Topper ---
Isn’t -mstrict-align the default? It is in LLVM.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115789
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #4 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115789
Jeffrey A. Law changed:
What|Removed |Added
Last reconfirmed||2024-07-04
Status|UNCONFIR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115789
--- Comment #2 from lu_zero at gentoo dot org ---
(In reply to Jeffrey A. Law from comment #1)
> If you still have the system, knowing the value of the registers at this
> point would be helpful. "info all-r" in gdb would give you that informati
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115789
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
--- Comment #1
12 matches
Mail list logo
