All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Khem Raj" <raj.khem@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	 Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] binutils: Upgrade to 2.35 release
Date: Sat, 1 Aug 2020 22:48:33 -0700	[thread overview]
Message-ID: <CAMKF1sop58PPx6M8Xc4GrfvS9AvOHrVe_GwgEDk8_2-3FXDZ6w@mail.gmail.com> (raw)
In-Reply-To: <b239d09f8e3d55103fb5aef84b2aebf5b13a8817.camel@linuxfoundation.org>

On Sat, Aug 1, 2020 at 3:12 AM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>
> On Thu, 2020-07-30 at 00:53 -0700, Khem Raj wrote:
> > assembler supports dwarf-5 format line numbers
> > linker has -M -MP gcc-like option
> >
> > for detailed release notes see [1]
> >
> > [1] https://lists.gnu.org/archive/html/info-gnu/2020-07/msg00008.html
> >
> > Signed-off-by: Khem Raj <raj.khem@gmail.com>
>
> This patch looks to be the cause of the perf failures you mentioned to
> me on irc:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/1225
>

I looked into the error a bit, it seems we need to backport a kernel
patch [1] to get this fixed

Bruce, Can you please schedule this backport and perhaps send kernel
updates for master which this patch
in

[1] https://github.com/torvalds/linux/commit/39efdd94e314336f4acbac4c07e0f37bdc3bef71

Thanks
-Khem

  reply	other threads:[~2020-08-02  5:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-30  7:53 [PATCH] binutils: Upgrade to 2.35 release Khem Raj
2020-07-30  8:02 ` ✗ patchtest: failure for " Patchwork
2020-08-01 10:12 ` [OE-core] [PATCH] " Richard Purdie
2020-08-02  5:48   ` Khem Raj [this message]
2020-08-02 17:36     ` Bruce Ashfield
2020-08-19  4:26 ` Scott Branden
2020-08-19  4:59   ` Alistair Francis
2020-08-19  6:39     ` Khem Raj
2020-08-19 16:09       ` Scott Branden

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAMKF1sop58PPx6M8Xc4GrfvS9AvOHrVe_GwgEDk8_2-3FXDZ6w@mail.gmail.com \
    --to=raj.khem@gmail.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.