public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug go/114453] New: 32-bit go.test/test/fixedbugs/issue16016.go FAILs Date: Mon, 25 Mar 2024 10:51:08 +0000 [thread overview] Message-ID: <bug-114453-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114453 Bug ID: 114453 Summary: 32-bit go.test/test/fixedbugs/issue16016.go FAILs Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: go Assignee: ian at airs dot com Reporter: ro at gcc dot gnu.org Target Milestone: --- Target: i386-pc-solaris2.11, sparc-sun-solaris2.11, i686-pc-linux-gnu The 32-bit go.test/test/fixedbugs/issue16016.go FAILs on most (all?) targets: FAIL: go.test/test/fixedbugs/issue16016.go execution, -O2 -g On Solaris, the error is like runtime: out of memory: cannot allocate 4194304-byte block (3779067904 in use) fatal error: out of memory while on Linux/i686 I get unable to allocate additional stack space: errno 1 SIGABRT: abort PC=0xf7ed3d99 m=6 sigcode=4294967290
next reply other threads:[~2024-03-25 10:51 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-25 10:51 ro at gcc dot gnu.org [this message] 2024-03-27 18:47 ` [Bug go/114453] " cvs-commit at gcc dot gnu.org 2024-03-27 18:48 ` ian at airs dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-114453-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).