[PATCH v6 00/10] New backend for the TI PRU processor

[Dimitar Dimitrov]

On вторник, 11 юни 2019 г. 14:04:41 EEST Jeff Law wrote:
> On 6/9/19 2:01 PM, Dimitar Dimitrov wrote:
> > This is the latest patch set for adding TI PRU I/O processor backend to
> > GCC. Comments from all previous series have been addressed [1], [2], [3],
> > [4], [5].> 
> > Test results can be downloaded from here:
> >    http://dinux.eu/gnupru/testresults/20190607-c16eb7019be/
> > 
> > Changes since patch series v5 [5] are minimal:
> > 
> > - A few whitespace and comment fixes.
> > - doloop_end_internal length expression fix.
> > - Define TARGET_HARD_REGNO_CALL_PART_CLOBBERED hook for PRU.
> > - Use uniform naming for the PRU register number constants.
> > 
> > [1] http://gcc.gnu.org/ml/gcc-patches/2018-06/msg00775.html
> > [2] http://gcc.gnu.org/ml/gcc-patches/2018-07/msg01779.html
> > [3] http://gcc.gnu.org/ml/gcc-patches/2018-08/msg00927.html
> > [4] http://gcc.gnu.org/ml/gcc-patches/2018-09/msg00392.html
> > [5] http://gcc.gnu.org/ml/gcc-patches/2018-10/msg00979.html
> > 
> > Regards,
> > Dimitar
> > 
> > Dimitar Dimitrov (10):
> >   Initial TI PRU GCC port
> >   Initial TI PRU libgcc port
> >   testsuite: Add PRU tests
> >   testsuite: Add check for overflowed IMEM region to testsuite
> >   testsuite: Add check for unsupported TI ABI PRU features to testsuite
> >   testsuite: Remove PRU from test cases requiring hosted environment
> >   testsuite: Define PRU stack usage
> >   testsuite: Mark that PRU has one-cycle jumps
> >   testsuite: Mark that PRU uses all function pointer bits
> >   testsuite: Mark testsuite that PRU has different calling convention
> 
> [ ... ]
> My recollection was this was all ready to go, so I'm going to ack with
> the only pre-commit requirement being to fix the issue Andreas pointed
> out with the 20101011-1.c test change.
> 
> Can you please fill out the write-after-approval form (list me as your
> sponsor)
> 
> https://sourceware.org/cgi-bin/pdw/ps_form.cgi
> 
> Jeff
I committed all the patches to trunk. The 20101011-1.c issue was fixed.

Thanks,
Dimitar