linux-kernel - Re: [PATCH] ARC: Explicitly specify OUTPUT

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <fa3f7d80855306d96dcaea52f5dc2b783d5bceb1.camel@synopsys.com>
Date:   Fri, 1 Jun 2018 16:43:14 +0000
From:   Alexey Brodkin <Alexey.Brodkin@...opsys.com>
To:     Vineet Gupta <Vineet.Gupta1@...opsys.com>
CC:     Cupertino Miranda <Cupertino.Miranda@...opsys.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Claudiu Zissulescu <Claudiu.Zissulescu@...opsys.com>,
        "linux-snps-arc@...ts.infradead.org" 
        <linux-snps-arc@...ts.infradead.org>
Subject: Re: [PATCH] ARC: Explicitly specify OUTPUT_FORMAT in the linker
 script

Hi Vineet,

On Fri, 2018-06-01 at 09:12 -0700, Vineet Gupta wrote:
> 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 ?

Right, this is preventive patch.
As Claus mentioned that's good to have this explicit information for BFD but
otherwise there's no clear requirement or even recommendation on OUTPUT_FORMAT
usage so that might not be needed.

-Alexey