scall/libcall_linux.go:217:19: error: use of undefined type
'_libgo_loff_t_type'
../../../libgo/go/syscall/libcall_linux.go:217:19: error: use of undefined type
'_libgo_loff_t_type'
make[4]: *** [Makefile:3038: syscall.lo] Error 1
>From config.log:
configure:15552: checking for loff
> Am 17.06.2022 um 22:34 schrieb Andrew Pinski via Gcc-patches
> :
>
> On Thu, Jun 16, 2022 at 3:59 AM Tamar Christina via Gcc-patches
> wrote:
>>
>> Hi All,
>>
>> For IEEE 754 floating point formats we can replace a sequence of alternative
>> +/- with fneg of a wider type followed by an f
Hi Peter,
On Fri, Jun 17, 2022 at 11:50:35PM -0500, Peter Bergner wrote:
> The initial commit that added opaque types thought that there couldn't
> be any valid initializations for variables of these types, but the test
> case in the bug report shows that isn't true. The solution is to handle
> O
ibcall_linux.go:217:19: error: use of undefined
> type '_libgo_loff_t_type'
> make[4]: *** [Makefile:3038: syscall.lo] Error 1
>
> From config.log:
>
> configure:15552: checking for loff_t
> configure:15552: /opt/gcc/gcc-20220618/Build/./gcc/xgcc
> -B/opt/g
On Jun 18 2022, Ian Lance Taylor wrote:
> What target?
aarch64-suse-linux, of course.
> What is the output of
>
> grep loff_t TARGET/libgo/gen-sysinfo.go
type ___loff_t int64
type _loff_t int64
type ___kernel_loff_t int64
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB4
Hi Harald,
we need to check the POS (and LEN) arguments of bit intrinsics
when simplifying, e.g. when used in array constructors.
Otherwise we ICE. Found by Gerhard.
The fix is straightforward, see attached.
Regtested on x86_64-pc-linux-gnu. OK for mainline?
OK.
Thanks for the patch!
Reg
