On 08.10.24 21:08, Jonathan Wakely wrote:
On Tue, 8 Oct 2024 at 20:02, Frank Scheiner <frank.schei...@web.de> wrote:
On 08.10.24 20:54, Jonathan Wakely wrote:
On Tue, 8 Oct 2024 at 18:43, Frank Scheiner <frank.schei...@web.de> wrote:
This was tested by bootstrapping GCC natively on ia64-t2-linux-gnu and
running the testsuite (based on
236116068151bbc72aaaf53d0f223fe06f7e3bac):
https://gcc.gnu.org/pipermail/gcc-testresults/2024-June/817268.html
For comparison, the same with just
236116068151bbc72aaaf53d0f223fe06f7e3bac:
https://gcc.gnu.org/pipermail/gcc-testresults/2024-June/817267.html
gcc/
* config/ia64/ia64.cc: Enable LRA for ia64.
* config/ia64/ia64.md: Likewise.
* config/ia64/predicates.md: Likewise.
Signed-off-by: René Rebe <r...@exactcode.de>
Who authored this patch?
Yeah, I wondered how this would work out with me sending it. Both
patches are authored by René.
If it was René that should be made clear so that whoever applies this
patch knows to use the right --author option to git.
I somehow missed that option and locally in my copy of GCC, René is
mentioned as the author by git for these commits. Should I send a v3?
That might be the clearest way to make sure that it gets applied
correctly, thanks.
On the way...
