public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/104775] New: [9/10/11/12 Regression] Failure to assemble on s390x with -fsanitize=undefined Date: Thu, 03 Mar 2022 21:41:57 +0000 [thread overview] Message-ID: <bug-104775-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104775 Bug ID: 104775 Summary: [9/10/11/12 Regression] Failure to assemble on s390x with -fsanitize=undefined Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jakub at gcc dot gnu.org Target Milestone: --- struct A { virtual long foo () const; int a; }; long A::foo () const { int sec = a / 0; return sec; } test with -O2 -w -m64 -march=zEC12 -fsanitize=undefined fails to assemble Music_Emu.s: Assembler messages: Music_Emu.s:56: Error: syntax error; missing ')' after base register Music_Emu.s:56: Error: junk at end of line: `%r12)' The regression appeared some time between r240000 and r245002 so during GCC 7 development, haven't bisected when exactly. The problematic assembly line is: clgte %r1,0(%r5,%r12)
next reply other threads:[~2022-03-03 21:41 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-03 21:41 jakub at gcc dot gnu.org [this message] 2022-03-03 21:42 ` [Bug target/104775] " jakub at gcc dot gnu.org 2022-03-03 21:57 ` jakub at gcc dot gnu.org 2022-03-04 13:53 ` jakub at gcc dot gnu.org 2022-03-07 10:15 ` cvs-commit at gcc dot gnu.org 2022-03-07 10:15 ` [Bug target/104775] [9/10/11 " jakub at gcc dot gnu.org 2022-03-29 5:53 ` cvs-commit at gcc dot gnu.org 2022-03-30 8:15 ` [Bug target/104775] [9/10 " jakub at gcc dot gnu.org 2022-05-10 8:24 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:25 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:36 ` jakub at gcc dot gnu.org
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-104775-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).