public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "elronnd at elronnd dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/97607] New: Spurious sign extension Date: Tue, 27 Oct 2020 23:54:55 +0000 [thread overview] Message-ID: <bug-97607-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97607 Bug ID: 97607 Summary: Spurious sign extension Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: elronnd at elronnd dot net Target Milestone: --- The following code extern void fun(char); void wrapper(char x) { fun(x); } Should compile 'wrapper' to a single jump, but instead it does this (on amd64): wrapper: movsx edi, dil jmp fun Presumably 'x' is getting promoted to int in wrapper, and the promotion never gets removed.
next reply other threads:[~2020-10-27 23:54 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-27 23:54 elronnd at elronnd dot net [this message] 2020-10-28 9:44 ` [Bug rtl-optimization/97607] " rguenth at gcc dot gnu.org 2021-03-04 21:03 ` [Bug target/97607] " pinskia at gcc dot gnu.org 2021-03-04 21:04 ` pinskia at gcc dot gnu.org 2021-03-04 23:57 ` pinskia 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-97607-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).