https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110297
Ian Lance Taylor changed:
What|Removed |Added
Resolution|--- |FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110297
--- Comment #6 from CVS Commits ---
The releases/gcc-13 branch has been updated by Ian Lance Taylor
:
https://gcc.gnu.org/g:4ac89ab35884906900cde8172d2db74e1d913fec
commit r13-7459-g4ac89ab35884906900cde8172d2db74e1d913fec
Author: Ian Lance
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110297
--- Comment #5 from CVS Commits ---
The master branch has been updated by Ian Lance Taylor :
https://gcc.gnu.org/g:efecb298d880cda20f8d7bea2d7b500a9752ce56
commit r14-1999-gefecb298d880cda20f8d7bea2d7b500a9752ce56
Author: Ian Lance Taylor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110297
--- Comment #4 from Ian Lance Taylor ---
Thanks. I suspect this was broken by
https://gcc.gnu.org/pipermail/gcc-patches/2022-October/604158.html.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110297
--- Comment #3 from Andreas Schwab ---
The problem is in the magic comment in libgo/go/runtine/mem_gccgo.go:
//extern mmap
func sysMmap(addr unsafe.Pointer, n uintptr, prot, flags, fd int32, off
_libgo_off_t_type) unsafe.Pointer
This needs to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110297
--- Comment #2 from Andreas Schwab ---
The go side of the mmap C function is using the wrong type for the offset
argument.
Dump of assembler code for function runtime.mmap:
0xb692c340 <+0>: push{r4, r5, lr}
0xb692c344 <+4>:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110297
Matthias Klose changed:
What|Removed |Added
Target|arm-linux-gnueabihf |arm-linux-gnueabihf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110297
Richard Biener changed:
What|Removed |Added
Keywords||testsuite-fail
Target Milestone|---
