Re: [PATCH 01/11] Initial TI PRU GCC port

2018-06-27 Thread Jeff Law
On 06/23/2018 09:42 AM, Dimitar Dimitrov wrote: >> >> I've already asked about your copyright assignment status. So you know, >> we can't go forward with any nontrivial contributions until the >> assignment is in place. > Yes, FSF has my assignment since November 2016. Great. Thanks. >> So i

Re: [PATCH 01/11] Initial TI PRU GCC port

2018-06-23 Thread Dimitar Dimitrov
On петък, 22 юни 2018 г. 12:20:46 EEST Jeff Law wrote: > On 06/13/2018 12:57 PM, Dimitar Dimitrov wrote: > > ChangeLog: > > > > 2018-06-13 Dimitar Dimitrov > > > > * configure: Regenerate. > > * configure.ac: Add PRU target. > > > > gcc/ChangeLog: > > > > 2018-06-13 Dimitar Dimitrov

Re: [PATCH 01/11] Initial TI PRU GCC port

2018-06-22 Thread Jeff Law
On 06/13/2018 12:57 PM, Dimitar Dimitrov wrote: > ChangeLog: > > 2018-06-13 Dimitar Dimitrov > > * configure: Regenerate. > * configure.ac: Add PRU target. > > gcc/ChangeLog: > > 2018-06-13 Dimitar Dimitrov > > * config/pru/pru-ldst-multiple.md: Generate using pru-ldst-

Re: [PATCH 01/11] Initial TI PRU GCC port

2018-06-18 Thread Dimitar Dimitrov
On сряда, 13 юни 2018 г. 19:44:16 EEST Joseph Myers wrote: > On Wed, 13 Jun 2018, Dimitar Dimitrov wrote: > > + error ("__delay_cycles() only takes constant arguments"); > > As in documentation, diagnostics should not use () to indicate that a name > refers to a function (as opposed to referr

Re: [PATCH 01/11] Initial TI PRU GCC port

2018-06-13 Thread Joseph Myers
On Wed, 13 Jun 2018, Dimitar Dimitrov wrote: > + error ("__delay_cycles() only takes constant arguments"); As in documentation, diagnostics should not use () to indicate that a name refers to a function (as opposed to referring to a call with no arguments). However, function names, option