From 1afab7a878555956f4842dcbed19bfe3c1c28a6e Mon Sep 17 00:00:00 2001 From: Ian Lance Taylor Date: Fri, 7 Jun 2019 21:16:11 +0000 Subject: compiler: improve write barrier generation For string, slice, interface values, do assignments field by field instead of using typedmemmove. Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/181297 From-SVN: r272055 --- gcc/go/gofrontend/expressions.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'gcc/go/gofrontend/expressions.h') diff --git a/gcc/go/gofrontend/expressions.h b/gcc/go/gofrontend/expressions.h index 6ba7fe1..22dd2fc 100644 --- a/gcc/go/gofrontend/expressions.h +++ b/gcc/go/gofrontend/expressions.h @@ -237,7 +237,7 @@ class Expression // Make an expression that evaluates to some characteristic of an string. // For simplicity, the enum values must match the field indexes in the - // underlying struct. + // underlying struct. This returns an lvalue. enum String_info { // The underlying data in the string. @@ -448,7 +448,7 @@ class Expression // Make an expression that evaluates to some characteristic of a // slice. For simplicity, the enum values must match the field indexes - // in the underlying struct. + // in the underlying struct. This returns an lvalue. enum Slice_info { // The underlying data of the slice. @@ -469,7 +469,7 @@ class Expression // Make an expression that evaluates to some characteristic of an // interface. For simplicity, the enum values must match the field indexes - // in the underlying struct. + // in the underlying struct. This returns an lvalue. enum Interface_info { // The type descriptor of an empty interface. -- cgit v1.1