On 22/09/14 14:30, James Greenhalgh wrote:
>
> On Thu, Sep 18, 2014 at 11:12:15AM +0100, Richard Earnshaw wrote:
>> On 18/09/14 10:53, James Greenhalgh wrote:
>>> +$(srcdir)/config/aarch64/aarch64-builtin-iterators.h:
>>> $(srcdir)/config/aarch64/geniterators.sh \
>>> + $(srcdir)/config/aarch
On Thu, Sep 18, 2014 at 11:12:15AM +0100, Richard Earnshaw wrote:
> On 18/09/14 10:53, James Greenhalgh wrote:
> > +$(srcdir)/config/aarch64/aarch64-builtin-iterators.h:
> > $(srcdir)/config/aarch64/geniterators.sh \
> > + $(srcdir)/config/aarch64/iterators.md
> > + $(SHELL) $(srcdir)/con
On Sep 18, 2014, at 3:12 AM, Richard Earnshaw wrote:
>
> Is there any real need to write this into the source directory and have
> the built file checked in? Ie. can't we always write to the build
> directory and use it from there.
I build part of my .md file from a C++ program, so I have to bu
On 18/09/14 10:53, James Greenhalgh wrote:
>
> Hi,
>
> A possible source of errors is in keeping the iterators.md file and the
> iterator macros in aarch64-builtin.c synchronized.
>
> Clearly this shouldn't be a problem given standard unix tools, it is just a
> text processing job.
>
> This pat
Hi,
A possible source of errors is in keeping the iterators.md file and the
iterator macros in aarch64-builtin.c synchronized.
Clearly this shouldn't be a problem given standard unix tools, it is just a
text processing job.
This patch adds geniterators.sh to the AArch64 backend which takes the
