You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Can't wait for P1040 std::embed (http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p1040r0.html …). gcc wants 12+ GB to build this (it's just that one 60 MB array). Might use "ld -r -b binary" or "objcopy -I binary" for now..pic.twitter.com/8IrIlQhEgp
Update: Using uint64_t instead of uint8_t significantly reduces gcc memory usage, but for some reason compile time explodes. Using a super large string constant compiles super fast and needs almost no memory. So I'm going with super-large string constant for now.pic.twitter.com/YlL9fqA3MM
Another Update: TIL that msvc only supports C string constants with a length of up to 64kB.
does removing the length specifier or declaring it as pointer (in the string literal case) change anything?
I haven't tried and building that project takes a while.. (I could create a nice stand-alone test case, but so could you and I have better things to do now that this is working for me.. :)
my guess: comma-separated array means the parser is to expect an expression after every comma, leading to allocation of a parser subnode, parsing of that expression; string can be parsed linearly and adds only one node to an AST. It's sad,though,because `xxd -i` is so handy!
Great to know! Thanks for sharing.
BTW you can optimize further by omitting double-0 prefixes for single-digit octal (esp. \000).
I think that would be cool! Feel free to include it. The project name is "nextpnr". I hope there will be a first public release soonish.
Clifford, what is the benefit of this over (for example) mmap-ing the data file?
On archs that support mmap it is equivalent, except that you don't need to locate the file. But we also want to be able to run that on archs without mmap support (such as bare metal). We support different ways of accessing those DBs. On win it's in a resource file for example.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
