On Jan 27, 2016 8:30 AM, "Mathieu Desnoyers" <[email protected]> wrote: > > ----- On Jan 27, 2016, at 6:59 AM, Mathieu Desnoyers < [email protected]> wrote: >> >> ----- On Jan 27, 2016, at 6:31 AM, Burton, Ross <[email protected]> wrote: >>> >>> >>> On 26 January 2016 at 23:14, Khem Raj <[email protected]> wrote: >>>> >>>> > Yes, we have narrowed down our problem to this specific patch by >>>> > removing the patch from the OE gcc patches, rebuilding gcc, and >>>> > then building our test program with that gcc. The problem goes >>>> > away when we do so, which points directly to that patch as a >>>> > culprit. >>>> > >>>> > Test program is attached. >>>> >>>> Ok I think we can remove this from master and jethro release >>> >>> >>> Mathieu, as you found this do you want the glory by submitting a the removal patch? >> >> >> Thanks for asking, but for me a >> >> Reported-by: Mathieu Desnoyers <[email protected]> >> >> in the patch commit messge is good enough. >> You'll probably want to have a link to this discussion thread >> also in the commit message. > > > I have a few minutes in front of me, I'll prepare a patch.
Ok. I think for jethro and master its ok, for other branches. This needs testing > > Thanks, > > Mathieu > >> >> >> Thanks, >> >> Mathieu >> >>> >>> Cheerss, >>> Ross >>> >> >> -- >> Mathieu Desnoyers >> EfficiOS Inc. >> http://www.efficios.com >> >> _______________________________________________ >> lttng-dev mailing list >> [email protected] >> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev > > > -- > Mathieu Desnoyers > EfficiOS Inc. > http://www.efficios.com
-- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
