On Thu, Mar 28, 2019 at 5:48 AM Burton, Ross wrote:
> On Tue, 26 Mar 2019 at 19:41, Andre McCurdy wrote:
> > > > +growing_stack = false
> > >
> > > this is mostly true for arches we support but maybe a comment
> > > to check it when doing explicit arch ports ( e.g. arm can grown both
> ways)
> >
On Tue, 26 Mar 2019 at 19:41, Andre McCurdy wrote:
> > > +growing_stack = false
> >
> > this is mostly true for arches we support but maybe a comment
> > to check it when doing explicit arch ports ( e.g. arm can grown both ways)
>
> Not on EABI or any other ARM ABI which could possibly be targeted
On Tue, Mar 26, 2019 at 11:08 AM Khem Raj wrote:
> On Tue, Mar 26, 2019 at 5:02 AM Ross Burton wrote:
> >
> > GLib wants to execute code to identify several properties of the system, for
> > example is vsprintf() broken and what direction does the stack grow. In
> > cross-compiled environments th
On Tue, Mar 26, 2019 at 5:02 AM Ross Burton wrote:
>
> GLib wants to execute code to identify several properties of the system, for
> example is vsprintf() broken and what direction does the stack grow. In
> cross-compiled environments these fallback to the default values which are not
> always co
GLib wants to execute code to identify several properties of the system, for
example is vsprintf() broken and what direction does the stack grow. In
cross-compiled environments these fallback to the default values which are not
always correct (our vsprintf() is fine, but the test assumes it isn't)
