On Fri, Jul 6, 2018 at 1:13 PM, Tamar Christina wrote:
>> >>
>> >> So I am curious as to why this shows up in Christophe's test but not
>> >> in any of your test runs or indeed the testruns with our scripts.
>> >>
>
> The test was changed before sending out, the individual entries moved to
> a
> >>
> >> So I am curious as to why this shows up in Christophe's test but not
> >> in any of your test runs or indeed the testruns with our scripts.
> >>
The test was changed before sending out, the individual entries moved to
a macro. I then verified the code generation and did not rerun it
On Fri, Jul 6, 2018 at 1:04 PM, Christophe Lyon
wrote:
> On Fri, 6 Jul 2018 at 13:56, Ramana Radhakrishnan
> wrote:
>>
>> On Fri, Jul 6, 2018 at 10:16 AM, Tamar Christina
>> wrote:
>> > Hi All,
>> >
>> > This fixes a -Wpedantic error with the testcase because of extra ; left
>> > after the
>>
On Fri, 6 Jul 2018 at 13:56, Ramana Radhakrishnan
wrote:
>
> On Fri, Jul 6, 2018 at 10:16 AM, Tamar Christina
> wrote:
> > Hi All,
> >
> > This fixes a -Wpedantic error with the testcase because of extra ; left
> > after the
> > functions.
> >
> > Regtested single test on aarch64-none-elf and
On Fri, Jul 6, 2018 at 10:16 AM, Tamar Christina
wrote:
> Hi All,
>
> This fixes a -Wpedantic error with the testcase because of extra ; left after
> the
> functions.
>
> Regtested single test on aarch64-none-elf and no issues.
>
> Committed under the GCC obvious rule.
So I am curious as to
