public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/40327] Use less instructions to add some constants to register Date: Wed, 03 Jun 2009 10:36:00 -0000 [thread overview] Message-ID: <20090603103614.30160.qmail@sourceware.org> (raw) In-Reply-To: <bug-40327-17659@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from steven at gcc dot gnu dot org 2009-06-03 10:36 ------- This code comes from the split2 (split insns after reload). So this is target specific. It surprises me that non-legitimate constants are accepted before reload on ARM (at least in thumb mode). It may be (and IMHO, probably is) better to split the constant early, e.g. during expand. A REG_EQUAL note can be used to remember the original value added. -- steven at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Component|rtl-optimization |target Ever Confirmed|0 |1 GCC build triplet|i686-linux | GCC host triplet|i686-linux | Last reconfirmed|0000-00-00 00:00:00 |2009-06-03 10:36:14 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40327
next prev parent reply other threads:[~2009-06-03 10:36 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-06-03 7:39 [Bug rtl-optimization/40327] New: " carrot at google dot com 2009-06-03 10:36 ` steven at gcc dot gnu dot org [this message] 2009-06-03 10:58 ` [Bug target/40327] " steven at gcc dot gnu dot org 2009-06-09 22:06 ` rearnsha at gcc dot gnu dot org 2009-06-13 12:49 ` rearnsha at gcc dot gnu dot org 2009-06-13 13:04 ` rearnsha at gcc dot gnu dot org 2009-06-13 23:45 ` steven at gcc dot gnu dot 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=20090603103614.30160.qmail@sourceware.org \ --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).