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/114463] New: go.test/test/fixedbugs/issue4458.go FAILs Date: Mon, 25 Mar 2024 11:24:31 +0000 [thread overview] Message-ID: <bug-114463-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114463 Bug ID: 114463 Summary: go.test/test/fixedbugs/issue4458.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: i?86-pc-solaris2.11, sparcv9-sun-solaris2.11 The go.test/test/fixedbugs/issue4458.go FAILs on Solaris in a weird way: FAIL: issue4458.go -O (test for errors, line 19) FAIL: issue4458.go -O (test for excess errors) The issue happens both for a 32-bit-default x86 compiler, generating either 32 or 64-bit-code: Excess errors: issue4458.go:19: error: method 'foo' is ambiguous A 64-bit-default x86 compiler is fine,though. OTOH on sparc, a 32-bit default compiler is fine while a 64-bit-default compiler shows the same issue.
next reply other threads:[~2024-03-25 11:24 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-25 11:24 ro at gcc dot gnu.org [this message] 2024-03-27 18:36 ` [Bug go/114463] " cvs-commit at gcc dot gnu.org 2024-03-27 18:36 ` 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-114463-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).