public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/97607] Spurious sign extension
Date: Wed, 28 Oct 2020 09:44:57 +0000 [thread overview]
Message-ID: <bug-97607-4-jKLF7EfM7d@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97607-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97607
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Target| |x86_64-linux
Last reconfirmed| |2020-10-28
Status|UNCONFIRMED |NEW
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
This is the TARGET_PROMOTE_PROTOTYPES target hook at play, directing the FEs to
emit the sign-extension and RTL expansion failing to elide it. Note the
x86 ABI does _not_ specify the incoming argument is sign-extended so it only
works for functions where all calls are generated by GCC.
IMHO TARGET_PROMOTE_PROTOTYPES should go away.
next prev parent reply other threads:[~2020-10-28 9:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 23:54 [Bug rtl-optimization/97607] New: " elronnd at elronnd dot net
2020-10-28 9:44 ` rguenth at gcc dot gnu.org [this message]
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-jKLF7EfM7d@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: link
Be 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).