Re: section attribute of compound literals

2018-09-14 Thread Jason A. Donenfeld
Hi Jim, That becomes a bit harder when there are many many items: https://git.zx2c4.com/WireGuard/tree/src/crypto/zinc/selftest/chacha20poly1305.h#n87 Here I'd like to use compound literals to avoid wasting space, as several members are variably sized. Unfortunately I can't do that per https://g

Re: section attribute of compound literals

2018-09-14 Thread Jim Wilson
On Fri, Sep 14, 2018 at 7:44 AM Jason A. Donenfeld wrote: > Assuming this is an array of a huge amount of > chacha20poly1305_testvec, I'm not sure if there's a syntax for me to > define the symbol inline with the declarations. Any ideas? Don't do it inline. u8[] __stuffdata key_value = ... ... .

Re: section attribute of compound literals

2018-09-14 Thread Jason A. Donenfeld
Hi Jim, On Thu, Sep 13, 2018 at 10:39 PM Jim Wilson wrote: > The > compound literal could have an address, but we don't have a way to > attach attributes to compound literals. Thanks for the confirmation of the problem. > Since your testcase already has a symbol in the right section, you could

Re: section attribute of compound literals

2018-09-13 Thread Jim Wilson
On 09/10/2018 10:46 PM, Jason A. Donenfeld wrote: Hello, I'd like to have a compound literal exist inside a certain linker section. However, it doesn't appear to work as I'd like: #define __stuffdata __attribute__((__section__("stuff"))) const u8 works[] __stuffdata = { 0x1, 0x2, 0x3, 0x4 }; co