Bug 88406 - [9 regression] Many 64-bit Solaris 10/SPARC execution tests FAIL
Summary: [9 regression] Many 64-bit Solaris 10/SPARC execution tests FAIL
Status: RESOLVED WONTFIX
Alias: None
Product: gcc
Classification: Unclassified
Component: go (show other bugs)
Version: 9.0
: P4 normal
Target Milestone: 9.5
Assignee: Ian Lance Taylor
URL:
Keywords: testsuite-fail
Depends on:
Blocks:
 
Reported: 2018-12-07 14:36 UTC by Rainer Orth
Modified: 2022-05-27 08:21 UTC (History)
0 users

See Also:
Host:
Target: sparc*-sun-solaris2.10
Build:
Known to work:
Known to fail:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rainer Orth 2018-12-07 14:36:05 UTC
Since the Go 1.11 merge, many (all?) 64-bit Solaris 10/SPARC execution tests
FAIL with

FAIL: cmd/go/internal/cache
runtime: memory allocated by OS [18446744071360741376, 18446744071427850240) not
 in usable address space: base outside usable address space
fatal error: memory reservation exceeds address space limit

runtime stack:

        :0

        :0

        :0

        :0

        :0

        :0

        :0

        :0
[...]
        :0
main
        /vol/gcc/src/hg/trunk/local/libgo/runtime/go-main.c:57
_start
        :0

Solaris 11/SPARC and Solaris/x86 are fine, though.
Comment 1 Ian Lance Taylor 2019-03-06 22:06:43 UTC
I don't seem to have access to a SPARC Solaris 10 box.

It seems like Solaris 10 is ignoring the address argument passed to mmap.  Does Solaris have an equivalent of strace that will show system calls?
Comment 2 ro@CeBiTec.Uni-Bielefeld.DE 2019-03-06 22:14:33 UTC
> --- Comment #1 from Ian Lance Taylor <ian at airs dot com> ---
> I don't seem to have access to a SPARC Solaris 10 box.

You do ;-)  Just log into s10-sparc.gcc at my site.  Last Friday's gcc
builds are still in /var/gcc/regression.

> It seems like Solaris 10 is ignoring the address argument passed to mmap.  Does
> Solaris have an equivalent of strace that will show system calls?

Sure: use truss (or truss -vall to get a more detailed interpretation of
the arguments).
Comment 3 Jakub Jelinek 2019-05-03 09:17:54 UTC
GCC 9.1 has been released.
Comment 4 Ian Lance Taylor 2019-05-17 20:50:42 UTC
Is this still worth investigating given that we've dropped support for Solaris 10?
Comment 5 ro@CeBiTec.Uni-Bielefeld.DE 2019-05-20 08:59:53 UTC
> --- Comment #4 from Ian Lance Taylor <ian at airs dot com> ---
> Is this still worth investigating given that we've dropped support for Solaris
> 10?

It depends: this single bug accounts for 91% of all testsuite failures
on Solaris 10/SPARC and it's a regression from GCC 8.  I'd put it this
way: if it's easy to analyze and fix, it would be nice to have it fixed
in the last release supporting Solaris 10.
Comment 6 Rainer Orth 2019-05-20 09:04:36 UTC
Not a GCC 10 regression: Solaris 10 support already removed.
Comment 7 Jakub Jelinek 2019-08-12 08:57:21 UTC
GCC 9.2 has been released.
Comment 8 Jakub Jelinek 2020-03-12 11:58:42 UTC
GCC 9.3.0 has been released, adjusting target milestone.
Comment 9 Richard Biener 2021-06-01 08:12:34 UTC
GCC 9.4 is being released, retargeting bugs to GCC 9.5.
Comment 10 Richard Biener 2022-05-27 08:21:31 UTC
Solaris 2.10 no longer supported, branch closed.