Steven Rostedt writes:
> On Tue, 15 May 2018 15:24:21 +1000
> Michael Ellerman wrote:
>
>> > Have you tried building all current archs with function tracing enabled
>> > to make sure this doesn't break any of them? I can do it if you want.
>>
>> We shouldn't need to should we? This is only tou
On Tue, 15 May 2018 15:24:21 +1000
Michael Ellerman wrote:
> > Have you tried building all current archs with function tracing enabled
> > to make sure this doesn't break any of them? I can do it if you want.
>
> We shouldn't need to should we? This is only touching powerpc specific
> code (if
On Tue, 15 May 2018 15:24:21 +1000
Michael Ellerman wrote:
> Steven Rostedt writes:
> > On Mon, 14 May 2018 13:52:27 +1000
> > Nicholas Piggin wrote:
> >> The powerpc toolchain can compile combinations of 32/64 bit and
> >> big/little endian, so it's convenient to consider, e.g.,
> >>
> >>
Steven Rostedt writes:
> On Mon, 14 May 2018 13:52:27 +1000
> Nicholas Piggin wrote:
>> The powerpc toolchain can compile combinations of 32/64 bit and
>> big/little endian, so it's convenient to consider, e.g.,
>>
>> `CC -m64 -mbig-endian`
>>
>> To be the C compiler for the purpose of invoki
On Mon, 14 May 2018 13:52:27 +1000
Nicholas Piggin wrote:
> The powerpc toolchain can compile combinations of 32/64 bit and
> big/little endian, so it's convenient to consider, e.g.,
>
> `CC -m64 -mbig-endian`
>
> To be the C compiler for the purpose of invoking it to build target
> artifacts
The powerpc toolchain can compile combinations of 32/64 bit and
big/little endian, so it's convenient to consider, e.g.,
`CC -m64 -mbig-endian`
To be the C compiler for the purpose of invoking it to build target
artifacts. So overriding the the CC variable to include thse flags
works for this p
