From: Jan Hubicka <jh@suse.cz>
To: Eric Botcazou <ebotcazou@libertysurf.fr>
Cc: Jan Hubicka <jh@suse.cz>, gcc@gcc.gnu.org
Subject: Re: Reload bug
Date: Wed, 09 Apr 2003 09:49:00 -0000 [thread overview]
Message-ID: <20030409085953.GF9102@kam.mff.cuni.cz> (raw)
In-Reply-To: <200304090121.54636.ebotcazou@libertysurf.fr>
> > How it did detected that?
>
> /* If the outer part is a word or smaller, INNER larger than a
> word and the number of regs for INNER is not the same as the
> number of words in INNER, then INNER will need reloading. */
> return (GET_MODE_SIZE (mode) <= UNITS_PER_WORD
> && GET_MODE_SIZE (GET_MODE (inner)) > UNITS_PER_WORD
> && ((GET_MODE_SIZE (GET_MODE (inner)) / UNITS_PER_WORD)
> != HARD_REGNO_NREGS (REGNO (inner), GET_MODE (inner))))
>
> > I believe it is just pessimization masking a bug as currently there is no
> > way how to realize that subreg:SI of MMX with offset 4 register is not
> > valid (and with offset 0 is).
>
> Of course, it's pessimization when offset ==0, but it's correctness when
> offset == 4. As for the choice between correctness and pessimization...
>
> > It should not get recognized earlier than in reload as we should not
> > allocate value with subreg undoable in MMX register into MMX register
> > (unless rest of insns dictates otherwise). We've chatted about this
> > with Richard
>
> Then the culprit is local alloc.
This is approximately what the patch I quoted does - it makes regclass
to realize that it can't change mode this way. (it is not correct
either as it prohibits (subreg:SI xmm:DI 0) that is valid but we don't
have interface to declare this properly.
>
> > No, it is valid for high parts too as long as the register is possible
> > (imagine the xmm being replaced by eax). I think we can add extra test
> > realizing how large the registers are when index is nonzero. This will
> > get bit tricky to get right when indexes are nonzero for lowparts.
>
> Then why not use ! lowpart?
Because you can still have (subreg:sI eax:DI 4)
Honza
>
> --
> Eric Botcazou
next prev parent reply other threads:[~2003-04-09 8:59 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 18:52 Eric Botcazou
2003-04-08 23:16 ` Jan Hubicka
2003-04-09 0:44 ` Jan Hubicka
2003-04-09 7:00 ` Eric Botcazou
2003-04-09 3:00 ` Eric Botcazou
2003-04-09 9:49 ` Jan Hubicka [this message]
2003-04-09 8:57 ` Eric Botcazou
2003-04-09 9:45 ` Jan Hubicka
2003-04-09 9:50 ` Eric Botcazou
2003-04-09 14:52 ` Jan Hubicka
2003-04-09 18:10 ` Eric Botcazou
2003-04-09 19:15 ` Jan Hubicka
2003-04-10 14:25 ` Eric Botcazou
2003-04-10 16:31 ` Jan Hubicka
2003-04-10 16:35 ` Jan Hubicka
2003-04-10 20:21 ` Eric Botcazou
2003-04-10 20:43 ` Jan Hubicka
2003-04-11 14:44 ` Eric Botcazou
2003-04-11 17:49 ` Jan Hubicka
2003-04-11 18:09 ` Jan Hubicka
2003-04-11 19:01 ` Jan Hubicka
2003-04-11 19:07 ` Jan Hubicka
2003-04-12 14:55 ` Eric Botcazou
2003-04-12 17:45 ` Jan Hubicka
2003-04-13 19:57 ` Eric Botcazou
2003-04-13 20:04 ` Jan Hubicka
2003-04-12 17:55 ` Make reload to avoid invalid subregs Jan Hubicka
2003-04-17 22:32 ` Richard Henderson
2003-04-10 20:51 ` Reload bug Dale Johannesen
2003-04-09 9:13 ` Eric Botcazou
2003-04-09 11:25 ` Jan Hubicka
2003-04-09 12:04 ` Eric Botcazou
2003-04-09 18:05 ` Jan Hubicka
2003-04-09 18:26 ` Eric Botcazou
2003-04-09 21:23 ` Richard Henderson
-- strict thread matches above, loose matches on Subject: below --
1999-09-01 8:40 Andreas Schwab
1999-09-02 0:32 ` Jeffrey A Law
1999-09-02 2:15 ` Andreas Schwab
1999-09-30 18:02 ` Andreas Schwab
1999-09-30 18:02 ` Jeffrey A Law
1999-09-30 18:02 ` Andreas Schwab
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=20030409085953.GF9102@kam.mff.cuni.cz \
--to=jh@suse.cz \
--cc=ebotcazou@libertysurf.fr \
--cc=gcc@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).