From: Andreas Schwab <schwab@suse.de>
To: law@cygnus.com
Cc: gcc@gcc.gnu.org
Subject: Re: Reload bug
Date: Thu, 30 Sep 1999 18:02:00 -0000 [thread overview]
Message-ID: <jeemgh4qwb.fsf@hawking.suse.de> (raw)
Message-ID: <19990930180200.S9QYvMCfVnRQrpnFC6CEexwfz1Rs2m5o0SYohWNFSbI@z> (raw)
In-Reply-To: <25863.936257014@upchuck.cygnus.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]
Jeffrey A Law <law@cygnus.com> writes:
|> I'll note this doesn't occur in the mainline tree, but I have no idea if that
|> is because the bug has actually been fixed or because we're just not triggering
|> the problem anymore.
I have been able to reproduce the bug with CVS-yesterday, but not right
now. I think this is due to the ia32 merge, due to the change in the
subdi3 pattern. With the yesterday's compiler the offending insn looked
like this before global alloc:
(insn 83 77 85 (parallel[
(set (reg/v:DI 26)
(minus:DI (reg:DI 31)
(reg:DI 38)))
(clobber (scratch:SI))
] ) 215 {subdi3} (insn_list 77 (nil))
(expr_list:REG_DEAD (reg:DI 38)
(expr_list:REG_UNUSED (scratch:SI)
(nil))))
with (reg:DI 31) being equivalent to the const_double. Today I'm getting
this:
(insn 251 74 80 (set (reg/v:DI 28)
(reg:DI 35)) 66 {*movdi_2} (nil)
(nil))
(insn 80 251 82 (parallel [
(set (reg/v:DI 28)
(minus:DI (reg/v:DI 28)
(reg:DI 41)))
(clobber (reg:CC 17 flags))
]) 179 {subdi3} (insn_list 74 (nil))
(expr_list:REG_DEAD (reg:DI 41)
(expr_list:REG_UNUSED (reg:CC 17 flags)
(nil))))
where (reg:DI 35) now contains the const_double.
Andreas.
--
Andreas Schwab "And now for something
schwab@suse.de completely different."
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
next prev parent reply other threads:[~1999-09-30 18:02 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-01 8:40 Andreas Schwab
1999-09-02 0:32 ` Jeffrey A Law
1999-09-02 2:15 ` Andreas Schwab [this message]
1999-09-30 18:02 ` Andreas Schwab
1999-09-30 18:02 ` Jeffrey A Law
1999-09-30 18:02 ` Andreas Schwab
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
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-10 20:51 ` 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
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=jeemgh4qwb.fsf@hawking.suse.de \
--to=schwab@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=law@cygnus.com \
/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).