From: Hans-Peter Nilsson <hp@bitrange.com>
To: "Maciej W. Rozycki" <macro@embecosm.com>
Cc: gcc-patches@gcc.gnu.org, Ulrich Weigand <uweigand@de.ibm.com>
Subject: Re: [PATCH] PR middle-end/103059: reload: Also accept ASHIFT with indexed addressing
Date: Fri, 5 Nov 2021 22:38:21 -0400 (EDT) [thread overview]
Message-ID: <alpine.BSF.2.20.16.2111052222560.50035@arjuna.pair.com> (raw)
In-Reply-To: <alpine.DEB.2.20.2111031202310.18331@tpp.orcam.me.uk>
On Wed, 3 Nov 2021, Maciej W. Rozycki wrote:
> Correct a `vax-netbsdelf' target regression ultimately caused by commit
> c605a8bf9270 ("VAX: Accept ASHIFT in address expressions") (needed for
> LRA) and as of commit 4a960d548b7d ("Avoid invalid loop transformations
> in jump threading registry.") causing a build error in libgcc:
>
> .../libgcc/libgcov-driver.c: In function 'gcov_do_dump':
> .../libgcc/libgcov-driver.c:686:1: error: insn does not satisfy its constraints:
> 686 | }
> | ^
> (insn 2051 2050 2052 185 (set (reg/f:SI 0 %r0 [555])
> (plus:SI (ashift:SI (mem/c:SI (plus:SI (reg/f:SI 13 %fp)
> (const_int -28 [0xffffffffffffffe4])) [40 %sfp+-28 S4 A32])
> (const_int 3 [0x3]))
> (plus:SI (reg/v/f:SI 9 %r9 [orig:176 fn_buffer ] [176])
> (const_int 24 [0x18])))) ".../libgcc/libgcov-driver.c":172:40 614 {movaddrdi}
> (nil))
> during RTL pass: postreload
[...]
> As noted in the commit description this has been regression-tested with
> commit 4a960d548b7d^. I'm running regression-testing with GCC 11 right
> now as well and expect results by the end of week.
>
> I was trying to chase another target I could use to regression-test this
> with that does do scaled indexed addressing while still using old reload.
> The i386 port would be a good candidate, but it has switched to LRA long
> ago with no option to use old reload, and I think there would be little
> point in adding one just for the sake of such verification. Do we have
> any other port actually that could be affected by this change?
That'd be cris-elf.
Your proposed patch reminded me of 6cb68940dcf9; giving reload a
reload-specific insn_and_split pattern to play with, matching
"mult" outside of a mem. I *guess* that's the CRIS-specific
replacement to c605a8bf9270.
brgds, H-P
next prev parent reply other threads:[~2021-11-06 2:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 13:53 Maciej W. Rozycki
2021-11-04 18:12 ` Jeff Law
2021-11-04 21:04 ` Maciej W. Rozycki
2021-11-04 23:47 ` Jeff Law
2021-11-05 0:18 ` Maciej W. Rozycki
2021-11-09 0:26 ` Jeff Law
2021-11-10 16:41 ` Maciej W. Rozycki
2021-11-23 19:04 ` Jeff Law
2021-11-24 13:20 ` Maciej W. Rozycki
2021-11-24 13:25 ` Richard Biener
2021-11-24 13:38 ` Maciej W. Rozycki
2021-11-06 2:38 ` Hans-Peter Nilsson [this message]
2021-11-07 21:22 ` Maciej W. Rozycki
2021-11-08 4:15 ` Hans-Peter Nilsson
2021-11-08 10:00 ` Maciej W. Rozycki
2021-11-12 23:22 ` Hans-Peter Nilsson
2021-11-07 21:24 ` Maciej W. Rozycki
2021-11-09 11:59 ` Maciej W. Rozycki
2021-11-08 19:55 ` Hans-Peter Nilsson
2021-11-09 12:11 ` Maciej W. Rozycki
2021-11-08 19:55 ` Hans-Peter Nilsson
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=alpine.BSF.2.20.16.2111052222560.50035@arjuna.pair.com \
--to=hp@bitrange.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=macro@embecosm.com \
--cc=uweigand@de.ibm.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).