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/113447] New: [14 regression] issue20185.go etc. FAIL
Date: Wed, 17 Jan 2024 14:59:15 +0000 [thread overview]
Message-ID: <bug-113447-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113447
Bug ID: 113447
Summary: [14 regression] issue20185.go etc. FAIL
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: *-*-solaris2.11, i686-pc-linux-gnu
Three Go tests started FAILing on 20231219, seen at least on 32 and 64-bit
Solaris/SPARC and x86 and Linux/x86_64:
+FAIL: issue20185.go -O (test for excess errors)
Excess errors:
issue20185.go:13: error: variable defined to nil type
+FAIL: issue33386.go -O (test for errors, line 21)
+FAIL: issue4085a.go -O (test for excess errors)
Excess errors:
issue4085a.go:13: error: floating-point constant truncated to integer
issue4085a.go:15: error: integer constant overflow
next reply other threads:[~2024-01-17 14:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 14:59 ro at gcc dot gnu.org [this message]
2024-01-17 14:59 ` [Bug go/113447] " ro at gcc dot gnu.org
2024-01-19 4:49 ` cvs-commit at gcc dot gnu.org
2024-01-19 4:53 ` 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-113447-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: link
Be 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).