search for: 7c72f988bf86f141af91ab2d7cd011d

...t;> >> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithu >> b.com%2fdotnet%2fllilc%2fblob%2fdd12743f9cdb5418f1c39b2cd756da1e8396a9 >> 22%2flib%2fJit%2fLLILCJit.cpp%23L299&data=01%7c01%7candya%40microsoft. >> com%7ce71168aad7ca4c98ee1f08d2cb024bf8%7c72f988bf86f141af91ab2d7cd011d >> b47%7c1&sdata=4LCM5dPAFSQZYdEV2jNoXbtIg79%2foS5%2bB8O2Nl3ZqT4%3d >> >> On Thu, Oct 1, 2015 at 10:45 AM, David Blaikie via llvm-dev >> <llvm-dev at lists.llvm.org> wrote: >>> Moving to the LLVM Dev list & cc'ing Lang. >>> >>>...

Thanks for the link! There’s some code there that looks extremely relevant to say the least. > On 1 Oct 2015, at 19:00, Hayden Livingston <halivingston at gmail.com> wrote: > > Maybe looking at their code might help: > > https://github.com/dotnet/llilc/blob/dd12743f9cdb5418f1c39b2cd756da1e8396a922/lib/Jit/LLILCJit.cpp#L299 > > On Thu, Oct 1, 2015 at 10:45 AM, David

.../na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithu >>>> b.com%2fdotnet%2fllilc%2fblob%2fdd12743f9cdb5418f1c39b2cd756da1e8396a9 >>>> 22%2flib%2fJit%2fLLILCJit.cpp%23L299&data=01%7c01%7candya%40microsoft. >>>> com%7ce71168aad7ca4c98ee1f08d2cb024bf8%7c72f988bf86f141af91ab2d7cd011d >>>> b47%7c1&sdata=4LCM5dPAFSQZYdEV2jNoXbtIg79%2foS5%2bB8O2Nl3ZqT4%3d >>>> >>>> On Thu, Oct 1, 2015 at 10:45 AM, David Blaikie via llvm-dev >>>> <llvm-dev at lists.llvm.org> wrote: >>>>> Moving to the LLVM Dev list & cc&...

...for testing this is to create and mount a > loop device [2] with a small file. > > [1]: > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wi > kipedia.org%2Fwiki%2F%2Fdev%2Ffull&data=02%7C01%7Cnsosnov%40microsoft. > com%7Cb97a7371538b4dbe9a7308d4c2ec5aa0%7C72f988bf86f141af91ab2d7cd011d > b47%7C1%7C0%7C636347767773809248&sdata=Cb2oduozc2IDCLvXZGG1C4i4hQA7FPs > 5jHmnFYbk7zQ%3D&reserved=0 > [2]: > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstack > overflow.com%2Fa%2F16044420%2F2055486&data=02%7C01%7Cnsosnov%40microso > ft.com%7Cb9...

...%2fgithu >> >>>> b.com >> %2fdotnet%2fllilc%2fblob%2fdd12743f9cdb5418f1c39b2cd756da1e8396a9 >> >>>> >> 22%2flib%2fJit%2fLLILCJit.cpp%23L299&data=01%7c01%7candya%40microsoft. >> >>>> >> com%7ce71168aad7ca4c98ee1f08d2cb024bf8%7c72f988bf86f141af91ab2d7cd011d >> >>>> b47%7c1&sdata=4LCM5dPAFSQZYdEV2jNoXbtIg79%2foS5%2bB8O2Nl3ZqT4%3d >> >>>> >> >>>> On Thu, Oct 1, 2015 at 10:45 AM, David Blaikie via llvm-dev >> >>>> <llvm-dev at lists.llvm.org> wrote: >> >>>&gt...

...2f%2fgithu> >> >>>> b.com <http://b.com/>%2fdotnet%2fllilc%2fblob%2fdd12743f9cdb5418f1c39b2cd756da1e8396a9 >> >>>> 22%2flib%2fJit%2fLLILCJit.cpp%23L299&data=01%7c01%7candya%40microsoft. >> >>>> com%7ce71168aad7ca4c98ee1f08d2cb024bf8%7c72f988bf86f141af91ab2d7cd011d >> >>>> b47%7c1&sdata=4LCM5dPAFSQZYdEV2jNoXbtIg79%2foS5%2bB8O2Nl3ZqT4%3d >> >>>> >> >>>> On Thu, Oct 1, 2015 at 10:45 AM, David Blaikie via llvm-dev >> >>>> <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.o...

On linux at least you can use `/dev/full` [1] to test writing to a full device. > echo 'foo' > /dev/full bash: echo: write error: No space left on device Although that won't be a perfect test for this case where part of the file is written successfully. An alternative suggestion for testing this is to create and mount a loop device [2] with a small file. [1]: