Update 'Proposal/ResearchProposal.gmi'
This commit is contained in:
parent
addc443c19
commit
7537616306
|
@ -82,3 +82,19 @@ that C might not be the best solution for this job.
|
|||
[3] https://bellard.org/tcc/
|
||||
[4] https://2019.asiabsdcon.org/proc-body-2019.pdf#page=13
|
||||
[5] https://ieeexplore.ieee.org/document/1004368
|
||||
|
||||
I know that I should make another file for spontaneous ideas, but
|
||||
I will put them here.
|
||||
|
||||
Let's say I have the following motivation: code that keeps the GNU
|
||||
legacy is hard to verify in some sense (because of the multitude of
|
||||
non-standard behaviours and of the complexity), what if we get rid
|
||||
of that and then try to formally analyze the code in order to better
|
||||
understand the security of OpenBSD. Would it be a good enough motivation?
|
||||
I don't know. To better strenghten this motivation, I need to see what
|
||||
are the disadvantages of using GNU software.
|
||||
|
||||
In a way I am pissed that I need to find this rocket-science motivations
|
||||
in order to be able to run my porting project. Why can't I just simply
|
||||
port OpenBSD to a new compiler and see what conclusions do I draw after
|
||||
I finish.
|
Loading…
Reference in New Issue