← Back to context Comment by bitbasher 15 hours ago Really looking forward to #embed, once the compilers catch up. Until then, Golang. 12 comments bitbasher Reply enriquto 15 hours ago This is not how C standards work. If it appears in the standard, it means that it is already implemented in some compilers (in that case, at least in gcc and clang). pjmlp 13 hours ago That isn't really how it goes, that is how it used to be up to C99. enriquto 13 hours ago Thanks for the correction! Do you know if there is a document from the standards body explaining the change in philosophy? 2 replies → f1shy 15 hours ago I do that with ld and objcopy:https://stackoverflow.com/questions/58815959/include-binary-... jpcfl 15 hours ago Or xxd --include <file> :) Keyframe 13 hours ago The anti-Rust approach! rfl890 15 hours ago Clang 19 has it. accelbred 14 hours ago I end up using a .S asm file with .incbin directives to embed files.#embed would be much nicer JonChesterfield 11 hours ago Incbin works just fine from inline asm fwiw flohofwoe 1 hour ago Inline assembly isn't supported for x86-64 and ARM on MSVC which unfortunately also means the incbin trick can't be used there anymore.
enriquto 15 hours ago This is not how C standards work. If it appears in the standard, it means that it is already implemented in some compilers (in that case, at least in gcc and clang). pjmlp 13 hours ago That isn't really how it goes, that is how it used to be up to C99. enriquto 13 hours ago Thanks for the correction! Do you know if there is a document from the standards body explaining the change in philosophy? 2 replies →
pjmlp 13 hours ago That isn't really how it goes, that is how it used to be up to C99. enriquto 13 hours ago Thanks for the correction! Do you know if there is a document from the standards body explaining the change in philosophy? 2 replies →
enriquto 13 hours ago Thanks for the correction! Do you know if there is a document from the standards body explaining the change in philosophy? 2 replies →
f1shy 15 hours ago I do that with ld and objcopy:https://stackoverflow.com/questions/58815959/include-binary-...
accelbred 14 hours ago I end up using a .S asm file with .incbin directives to embed files.#embed would be much nicer JonChesterfield 11 hours ago Incbin works just fine from inline asm fwiw flohofwoe 1 hour ago Inline assembly isn't supported for x86-64 and ARM on MSVC which unfortunately also means the incbin trick can't be used there anymore.
JonChesterfield 11 hours ago Incbin works just fine from inline asm fwiw flohofwoe 1 hour ago Inline assembly isn't supported for x86-64 and ARM on MSVC which unfortunately also means the incbin trick can't be used there anymore.
flohofwoe 1 hour ago Inline assembly isn't supported for x86-64 and ARM on MSVC which unfortunately also means the incbin trick can't be used there anymore.
This is not how C standards work. If it appears in the standard, it means that it is already implemented in some compilers (in that case, at least in gcc and clang).
That isn't really how it goes, that is how it used to be up to C99.
Thanks for the correction! Do you know if there is a document from the standards body explaining the change in philosophy?
2 replies →
I do that with ld and objcopy:
https://stackoverflow.com/questions/58815959/include-binary-...
Or
:)
The anti-Rust approach!
Clang 19 has it.
I end up using a .S asm file with .incbin directives to embed files.
#embed would be much nicer
Incbin works just fine from inline asm fwiw
Inline assembly isn't supported for x86-64 and ARM on MSVC which unfortunately also means the incbin trick can't be used there anymore.