From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Cupertino Miranda" <Cupertino.Miranda@synopsys.com>,
Claudiu Zissulescu <Claudiu.Zissulescu@synopsys.com>
Subject: Re: [PATCH] ARC: Explicitly specify OUTPUT_FORMAT in the linker script
Date: Fri, 1 Jun 2018 09:12:14 -0700 [thread overview]
Message-ID: <05b33c2b-6fb4-6a51-c52b-a0b1012a1000@synopsys.com> (raw)
In-Reply-To: <20180601104904.48481-1-abrodkin@synopsys.com>
On 06/01/2018 03:49 AM, Alexey Brodkin wrote:
> It might be a good idea to explicitly specify BFD format
> depending on -EB/-EL option passed to the linker and not rely on
> default behavior as we have now.
What exactly is the problem we are trying to solve here ?
Is this preventive or did you run into something - if latter can u explain it here
please ?
> Description of the OUTPUT_FORMAT command is available here:
> https://sourceware.org/binutils/docs/ld/Format-Commands.html#Format-Commands
>
> Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
> Cc: Cupertino Miranda <cmiranda@synopsys.com>
> Cc: Claudiu Zissulescu <claziss@synopsys.com>
> ---
> arch/arc/kernel/vmlinux.lds.S | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arc/kernel/vmlinux.lds.S b/arch/arc/kernel/vmlinux.lds.S
> index f35ed578e007..0a1affc56d76 100644
> --- a/arch/arc/kernel/vmlinux.lds.S
> +++ b/arch/arc/kernel/vmlinux.lds.S
> @@ -11,6 +11,7 @@
> #include <asm/page.h>
> #include <asm/thread_info.h>
>
> +OUTPUT_FORMAT("elf32-littlearc", "elf32-bigarc", "elf32-littlearc")
> OUTPUT_ARCH(arc)
> ENTRY(res_service)
>
next prev parent reply other threads:[~2018-06-01 16:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 10:49 Alexey Brodkin
2018-06-01 16:12 ` Vineet Gupta [this message]
2018-06-01 16:43 ` Alexey Brodkin
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=05b33c2b-6fb4-6a51-c52b-a0b1012a1000@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=Claudiu.Zissulescu@synopsys.com \
--cc=Cupertino.Miranda@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®