[Bug c/96399] New: Arithmetic shift with vector extension becomes logical right shift on s390x

2020-07-31 Thread yohei at jp dot ibm.com
: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: yohei at jp dot ibm.com Target Milestone: --- When I applied arithmetic shift (>>) to a 16-element signed char vector variable, I observed behavior of logical right sh

[Bug c/96399] Arithmetic shift with vector extension becomes logical right shift on s390x

2020-07-31 Thread yohei at jp dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96399 --- Comment #1 from Yohei Ueda --- Output of gcc -v: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/s390x-linux-gnu/10.2.0/lto-wrapper Target: s390x-linux-gnu Configured with: /usr/src/gcc/configure --build=s390

[Bug go/63731] New: Fallback to netgo does not work

2014-11-04 Thread yohei at jp dot ibm.com
Assignee: ian at airs dot com Reporter: yohei at jp dot ibm.com CC: cmang at google dot com When the DNS resolver with CGO fails for statically linked binaries, it should fall back to the pure-go DNS resolver, if I understand correctly. This fallback mechanism does work at

[Bug go/63731] Fallback to netgo does not work

2014-11-13 Thread yohei at jp dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63731 --- Comment #1 from Yohei Ueda --- Created attachment 33966 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33966&action=edit Fix the DNS lookup problem for statically linked binaries I created a patch file that fixes this problem.

[Bug go/63731] Fallback to netgo does not work

2014-11-13 Thread yohei at jp dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63731 --- Comment #2 from Yohei Ueda --- I tested this issue with the latest GC trunk again, and noticed that GC always compiles programs that contains DNS lookups with dynamic linking even if -static is specified. $ go version go version devel +ae495

[Bug go/63731] Fallback to netgo does not work

2014-11-17 Thread yohei at jp dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63731 --- Comment #4 from Yohei Ueda --- Thank you for the correction. I need to use the following instructions to enable netgo with GC. $ go version go version devel +ae495517bd72 Fri Nov 14 11:43:01 2014 +1100 linux/amd64 $ go build -ldflags '-link

[Bug go/63731] Fallback to netgo does not work

2014-11-17 Thread yohei at jp dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63731 --- Comment #8 from Yohei Ueda --- If we can distinguish between the "not found" errors due to invalid host names and no nss, we can fall back to netgo only when nss is not available. I noticed that errno is set to 0 for invalid hostnames, and i

[Bug go/63731] Fallback to netgo does not work

2014-11-18 Thread yohei at jp dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63731 --- Comment #10 from Yohei Ueda --- https://code.google.com/p/go/source/browse/src/net/lookup_unix.go#63 func lookupIP(host string) (addrs []IP, err error) { addrs, err, ok := cgoLookupIP(host) if !ok { addrs, err

[Bug go/63731] Fallback to netgo does not work

2014-11-19 Thread yohei at jp dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63731 --- Comment #12 from Yohei Ueda --- "pure-Go goLookupIP" means that goLookupIP is written in Go as usual. https://code.google.com/p/go/source/browse/src/net/dnsclient_unix.go#364 cgoLookupIP uses getaddrinfo via CGO unless the netgo tag is set.

[Bug go/63731] Fallback to netgo does not work

2014-11-20 Thread yohei at jp dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63731 --- Comment #14 from Yohei Ueda --- I am not the original author, so my description may be inaccurate. > why isn't this "fallback" code always built for GO and available > to run instead of waiting until it hits this situation and then > built

[Bug go/63731] Fallback to netgo does not work

2014-12-03 Thread yohei at jp dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63731 --- Comment #20 from Yohei Ueda --- I noticed a Docker issue saying GC 1.4 does not rebuild the standard library with -a. https://github.com/docker/docker/issues/9449 I think the problem is now not limited to GCCGO.