mirror of
https://github.com/hanzoai/visor.git
synced 2026-09-24 17:04:14 +00:00
`go tool objdump` produces relative offsets for BL instructions as a number of instructions rather than a number of bytes. Calculate the byte offset ourselves. Example passing run on ARM machine: https://buildkite.com/gvisor/pipeline/builds/14732#018106ac-ac8e-4636-9a5a-bde1641b1175 Filed bug upstream about confusing output here: https://github.com/golang/go/issues/53117 PiperOrigin-RevId: 452137751
21 lines
741 B
Go
21 lines
741 B
Go
// Copyright 2022 The gVisor Authors.
|
|
//
|
|
// Licensed under the Apache License, Version 2.0 (the "License");
|
|
// you may not use this file except in compliance with the License.
|
|
// You may obtain a copy of the License at
|
|
//
|
|
// http://www.apache.org/licenses/LICENSE-2.0
|
|
//
|
|
// Unless required by applicable law or agreed to in writing, software
|
|
// distributed under the License is distributed on an "AS IS" BASIS,
|
|
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
// See the License for the specific language governing permissions and
|
|
// limitations under the License.
|
|
|
|
package checkescape
|
|
|
|
// fixOffset does nothing on amd64.
|
|
func fixOffset(fields []string, target string) (string, error) {
|
|
return target, nil
|
|
}
|