>>> On 02.02.18 at 14:03, <andrew.coop...@citrix.com> wrote:
> On 07/12/17 14:06, Jan Beulich wrote:
>> This allows the section contents to be disassembled without going
>> through any extra hoops, simplifying the analysis of problems in test
>> and/or emulation code.
>> The blobs being emitted as (r/o) data means we need to accept an
>> assembler warning here (about the differing section attributes).
>> Signed-off-by: Jan Beulich <jbeul...@suse.com>
> What about just giving up their constness? This is a test program after
Then the conflict would be in two attributes (writable and
executable) rather than just one. The issue is that we emit them
as data, but want them to be in an executable section. If anything
we'd have to re-do how they're emitted (e.g. by using asm()), but
that seems overkill to me.
Xen-devel mailing list