[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150514023259.GA17573@brightrain.aerifal.cx>
Date: Wed, 13 May 2015 22:32:59 -0400
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: Re: [PATCH v2] First prototype of script which adds CFI
directives to x86 asm
On Wed, May 13, 2015 at 07:36:46PM +0200, Alex Dowad wrote:
> Thanks to Szabolcs Nagy for your reply!
>
> > it might make sense to have a make rule that produces the cfi asm for inspection
>
> Any opinions from others on this?
I'm not sure. It's more clutter. It could be useful for debugging
issues, but so could intermediate .s files from the compiler before
making .o files, and in that case you just have to make them manually
if you want.
> > i wonder if a configure check for .cfi support should be added: in theory
> > an assembler may not support it (tcc?)
>
> Sure, I can do this. If debugging is not enabled, it doesn't make much sense
> to use the CFI script either.
>
> Would adding another variable to config.mak, something like GENERATE_CFI=yes
> (or something like that) be acceptable?
Perhaps configure should generate an AS_CMD variable or something,
making it just plain $CC for non-debug builds or when the CFI stuff
isn't supported, and something that wraps the call to $CC when CFI is
supported and desired (debug).
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
