[Bug testsuite/97699] [11 regression] zero-scratch-regs tests fail on arm

2021-02-23 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97699

Richard Biener  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #4 from Richard Biener  ---
dup

*** This bug has been marked as a duplicate of bug 97680 ***

[Bug testsuite/97699] [11 regression] zero-scratch-regs tests fail on arm

2021-01-14 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97699

Richard Biener  changed:

   What|Removed |Added

   Priority|P3  |P1

[Bug testsuite/97699] [11 regression] zero-scratch-regs tests fail on arm

2020-11-04 Thread burnus at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97699

Tobias Burnus  changed:

   What|Removed |Added

 CC||burnus at gcc dot gnu.org

--- Comment #3 from Tobias Burnus  ---
(In reply to Christophe Lyon from comment #0)
> BTW, there's a typo in the error message, it should say
> fzero-call-used-regs rather than fzero-call-used_regs (that is '-' instead
> of '_' before 'regs')

That one I fixed as obvious in
r11-4721-g243492e2c69741b91dbfe3bba9b772f65fc9354c


Otherwise, Richard S wrote regarding the FAIL + sorry:
https://gcc.gnu.org/pipermail/gcc-patches/2020-November/558041.html

> these are a signal to target maintainers that they need
> to decide whether to add support or accept the status quo
> (in which case a new effective-target will be needed).  See:
> https://gcc.gnu.org/pipermail/gcc-patches/2020-October/557595.html:
>
>The new tests are likely to fail on some targets with the sorry()
>message, but I think target maintainers are best placed to decide
>whether (a) that's a fundamental restriction of the target and the
>tests should just be skipped or (b) the target needs to implement
>the new hook.

[Bug testsuite/97699] [11 regression] zero-scratch-regs tests fail on arm

2020-11-03 Thread qinzhao at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97699

qinzhao at gcc dot gnu.org changed:

   What|Removed |Added

 CC||qinzhao at gcc dot gnu.org

--- Comment #2 from qinzhao at gcc dot gnu.org ---
this might be expected behavior since the implementation should work for
aarch64 and x86. 
other platforms either need to skip this testing or finish the implementation
at backend.