public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "siddhesh at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug build/28680] New: i686 builds broken with -ftree-vectorize Date: Fri, 10 Dec 2021 16:48:57 +0000 [thread overview] Message-ID: <bug-28680-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=28680 Bug ID: 28680 Summary: i686 builds broken with -ftree-vectorize Product: glibc Version: 2.35 Status: NEW Severity: normal Priority: P2 Component: build Assignee: unassigned at sourceware dot org Reporter: siddhesh at sourceware dot org CC: carlos at redhat dot com Target Milestone: --- See also: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103646 How to reproduce: configure with vectorizer enabled: $ ../configure --prefix=/usr CC="gcc -m32" CXX="g++ -m32" CFLAGS="-O2 -g -Wp,-D_GLIBCXX_ASSERTIONS -m32 -march=i686 -mtune=generic -msse2 -mfpmath=sse -mstackrealign -fasynchronous-unwind-tables -fstack-clash-protection -ftree-vectorize" --build=i686-redhat-linux Actual results: ../sysdeps/unix/sysv/linux/select.c: In function ‘__select64’: ../sysdeps/unix/sysv/linux/select.c:117:1: error: bp cannot be used in ‘asm’ here 117 | } | ^ make[2]: *** [/home/siddhesh/src/upstream/glibc/build-32/sysd-rules:229: /home/siddhesh/src/upstream/glibc/build-32/misc/select.os] Error 1 Expected results: Successful build. Additional Information: The vectorizer may end up having to realign stack and hence use up ebp, making it unavailable as a logal register variable. Adapting the configure test to account for vectorization may prove to be flaky, so it probably makes sense to simply disable the 6 argument syscall inlining if the vectorizer is enabled since the vectorizer gains may potentially outstrip the benefit of the inlining. This will become a wider issue with gcc12, where the vectorizer is enabled at -O2. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-12-10 16:48 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-10 16:48 siddhesh at sourceware dot org [this message] 2021-12-10 16:49 ` [Bug build/28680] " siddhesh at sourceware dot org 2021-12-10 17:01 ` fweimer at redhat dot com 2021-12-10 17:48 ` siddhesh at sourceware dot org 2022-01-10 16:25 ` [Bug libc/28680] " fweimer at redhat dot com
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=bug-28680-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.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: linkBe 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).