public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "georgjohann at web dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/32790] REG_N_SETS holds wrong value
Date: Tue, 17 Jul 2007 11:13:00 -0000 [thread overview]
Message-ID: <20070717111324.22808.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32790-11621@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from georgjohann at web dot de 2007-07-17 11:13 -------
(In reply to comment #1)
>
> This comes from the begining of time :).
> ZERO_EXTRACT has been there since the begining of time also:
> 70 kenner DEF_RTL_EXPR(ZERO_EXTRACT, "zero_extract", "eee", 'b')
>
So what is the conclusion...?
At least the following backends implement "insv" as
(define_*** "insv"
[(set (zero_extract (match_operand 0 ...
with a predicate that allows registers:
i386, pa, sh, c4x, arm, vax, ia64, m68k, ip2k, ns32k, rs6000, h8300, mcore
Uses of REG_N_SETS(*) are spread all over the RTL passes and many of them rely
on REG_N_SETS(*) == 1 etc.
If such a condition holds but is incorrect because (set (zero_extract is
ignored that may lead to a bug in the output, e.g. due to a wrong replacement.
--
georgjohann at web dot de changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |minor
Version|4.3.0 |unknown
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32790
next prev parent reply other threads:[~2007-07-17 11:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 10:00 [Bug rtl-optimization/32790] New: " georgjohann at web dot de
2007-07-17 10:23 ` [Bug rtl-optimization/32790] " pinskia at gcc dot gnu dot org
2007-07-17 11:13 ` georgjohann at web dot de [this message]
[not found] <bug-32790-4@http.gcc.gnu.org/bugzilla/>
2015-01-17 7:25 ` law at gcc dot gnu.org
2015-01-17 7:28 ` law 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=20070717111324.22808.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: 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).