public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-4869] syscall: add missing type conversion
Date: Mon, 23 Oct 2023 21:03:47 +0000 (GMT)	[thread overview]
Message-ID: <20231023210347.4AC573858C66@sourceware.org> (raw)

https://gcc.gnu.org/g:2621bd1bac614b63e52d0deb4ab2ff287a9fafa8

commit r14-4869-g2621bd1bac614b63e52d0deb4ab2ff287a9fafa8
Author: Ian Lance Taylor <iant@golang.org>
Date:   Thu Oct 19 16:46:14 2023 -0700

    syscall: add missing type conversion
    
    The gofrontend incorrectly accepted code that was missing a type conversion.
    The test case for this is bug518.go in https://go.dev/cl/536537.
    Future CLs in this series will detect the type error.
    
    Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/536638

Diff:
---
 gcc/go/gofrontend/MERGE    | 2 +-
 libgo/go/syscall/errstr.go | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/go/gofrontend/MERGE b/gcc/go/gofrontend/MERGE
index 398d2671b64d..0f961157dfd1 100644
--- a/gcc/go/gofrontend/MERGE
+++ b/gcc/go/gofrontend/MERGE
@@ -1,4 +1,4 @@
-c201fa2a684ada551ca9a0825a3075a0a69498de
+081ec9824a74ec9d82628d8d2f6b9a7a4c35a529
 
 The first line of this file holds the git revision number of the last
 merge done from the gofrontend repository.
diff --git a/libgo/go/syscall/errstr.go b/libgo/go/syscall/errstr.go
index 9f688e2a0c7b..02f228adc59d 100644
--- a/libgo/go/syscall/errstr.go
+++ b/libgo/go/syscall/errstr.go
@@ -24,7 +24,7 @@ func Errstr(errnum int) string {
 			}
 			return string(b[:i])
 		}
-		if errno != ERANGE {
+		if Errno(errno) != ERANGE {
 			return "strerror_r failure"
 		}
 	}

                 reply	other threads:[~2023-10-23 21:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20231023210347.4AC573858C66@sourceware.org \
    --to=ian@gcc.gnu.org \
    --cc=gcc-cvs@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).