public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/25703] [4.2 Regression] ACATS cxa4024 failure
Date: Wed, 25 Jan 2006 20:15:00 -0000 [thread overview]
Message-ID: <20060125201539.25822.qmail@sourceware.org> (raw)
In-Reply-To: <bug-25703-7210@http.gcc.gnu.org/bugzilla/>
------- Comment #13 from ebotcazou at gcc dot gnu dot org 2006-01-25 20:15 -------
> My apologies once again for the inconvenience. In the previous version of the
> patch I'd mistakenly assumed that STRICT_LOW_PART was some indication that the
> SUBREG only affected the "low_part". Investigating Jan's testcase with
> -mtune=i486, I now understand it really means STRICT_SUB_PART, and actually
> behaves identically to SUBREG in this optimization, as we preserve all of the
> unaffected bits anyway!
You're right, the manual doesn't seem to allow that kind of STRICT_LOW_PARTs:
`(strict_low_part (subreg:M (reg:N R) 0))'
This expression code is used in only one context: as the
destination operand of a `set' expression. In addition, the
operand of this expression must be a non-paradoxical `subreg'
expression.
The presence of `strict_low_part' says that the part of the
register which is meaningful in mode N, but is not part of mode M,
is not to be altered. Normally, an assignment to such a subreg is
allowed to have undefined effects on the rest of the register when
M is less than a word.
Is that a typo in the manual? What happens on big-endian?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25703
next prev parent reply other threads:[~2006-01-25 20:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-06 22:12 [Bug ada/25703] New: ACATS FAIL cxa4024 Ada.Strings.Maps on x86-linux laurent at guerby dot net
2006-01-24 12:25 ` [Bug ada/25703] [4.2 Regression] ACATS cxa4024 failure ebotcazou at gcc dot gnu dot org
2006-01-24 13:17 ` ebotcazou at gcc dot gnu dot org
2006-01-24 18:44 ` ebotcazou at gcc dot gnu dot org
2006-01-24 21:37 ` [Bug rtl-optimization/25703] " ebotcazou at gcc dot gnu dot org
2006-01-25 1:05 ` roger at eyesopen dot com
2006-01-25 13:52 ` ebotcazou at gcc dot gnu dot org
2006-01-25 18:19 ` hjl at lucon dot org
2006-01-25 18:27 ` ebotcazou at gcc dot gnu dot org
2006-01-25 18:41 ` hjl at lucon dot org
2006-01-25 18:59 ` ebotcazou at gcc dot gnu dot org
2006-01-25 19:53 ` roger at eyesopen dot com
2006-01-25 20:15 ` hjl at lucon dot org
2006-01-25 20:15 ` ebotcazou at gcc dot gnu dot org [this message]
2006-01-25 20:47 ` hjl at lucon dot org
2006-01-25 20:54 ` ebotcazou at gcc dot gnu dot org
2006-01-26 2:48 ` sayle at gcc dot gnu dot org
2006-01-26 7:04 ` ebotcazou 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=20060125201539.25822.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).