On 12/9/20 6:12 AM, abebeos via Gcc-patches wrote:
> Essence:
>
> I need a confirmation that the testsuite setup as presented in:
>
> https://github.com/abebeos/avr-gnu
>
> works fine.
>
> The problem with the avr target is that the testsuite cannot be run easily,
> mainly because of the need for a special simulated-target setup, which does
> not work for avr as documented. This led developers to a dead-end with
> their non-cc0-avr-backends (the non-cc0 backend is needed thus avr is not
> dropped from gcc11).
>
> I integrated a toolchain/testsetup to be able to run the gcc testsuite
> against a simulated avr target.
>
> I then used this toolchain to test 2 different existent
> non-cc0-avr-backends (from pipcet and saaadhu, both github).
>
> The result is that saaadhu's backend seems to be working 100%. It has
> identical testsuite results with the existing (but deprecated) cc0-backend,
> which means that it can be used "as-is" for inclusion in gcc11.
>
> Please note that I did this work in context of a bounty @ bountysouce, more
> information within the issue:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729#c35
I haven't looked at the github repo. But I do have a couple comments here.
First, the author of the changes (pipcet and saaadhu) need to have
copyright assignments on file with the FSF. Otherwise we can not use
their work at all.
Second, the work needs to be submitted for inclusion. I don't recall
seeing an official submission from either of them to gcc-patches.
I'm definitely curious about the testing setup and whether or not it can
be replicated into our Jenkins setup. It is my understanding there is
no newlib support for avr so I'm curious what you're using for a basic
runtime library.
jeff
