> We are happy to announce the release of GNU Mes 0.26.1.
Great work everyone ^_^
-Jeremiah
with:
NEVER TRUST ANYTHING IN HERE
I could be evil after all
-Jeremiah
r all after that you can leverage sha256sums and chains of
trust to do the rest
> I saw a project a while ago with an interesting approach that looks very
> interesting for tackling this problem: crowd-sourced, social code
> review:
> https://github.com/crev-dev/crev
Looks interesting
-Jeremiah
n in the Haskell Subset supported by blynn-compiler
which has been bootstrapped.
We have to think long term here, because we are going to have to support the
bootstrap forever.
And porting to new architectures and Operating Systems is going to be something
we will have to deal with.
- Jeremiah
st attractive.
>> And would be faster if MesCC running on guile was used as the lone bootstrap
>> seed.
> What do you mean? Faster in what sense?
Guile is a faster scheme than mes.c
-Jeremiah
e same as "lsl r1, #4"--drops the "#2" silently.
4 << 2 is 16. Log2(16) == 4; sounds about right
-Jeremiah
benefit Guix (and other distros I
> guess!) to have a fully built-from-source Haskell platform.
Indeed
-Jeremiah
ely such a change would occur as macro-less scheme is
no more productive than standard C coding.
- Jeremiah
e you'll have to waste 3.7bytes on average per malloc to always pad to
the 8byte boundary.
-Jeremiah
get it to enough guile compatibility; then it becomes:
once you have Gnu Mes, you are already bootstrapped.
^_^
- Jeremiah
Amazing work as always janneke.
We will just have to do some kaem work to make it work all on POSIX systems.
-Jeremiah
250byte hex0 hex assembler and a 737byte shell
-Jeremiah
the world)
>This should be great. :-)
That is the plan but we really could use more scheme programmers.
(Ambitious goals and all that)
-Jeremiah
be cool? !! ;-)
Indeed, hence why the solving of the Linux/POSIX bootstrap problem can be
solved with M2-Planet and stage0
Need more help though to get it all done faster
-Jeremiah
> Thank you for all your contributions!
> e.g., hex0 is amazing! :-)
Hex0 is only about 3 hours of work
This however is taking me months
https://github.com/oriansj/mes-m2
and when done will result in solving multiple bootstrapping problems
-Jeremiah
eds to be fixed
> Writting a Scheme compiler should be easy, if we don't care about
> optimization techniques. It doesn't need that requirements.
> But if you need any help in the low level area, I can help you guys.
Well I need more help in the high level areas
-Jeremiah
memory 10M && meld foo1 tape_02
If you need further clarification, I am more than happy to help
Plus there are some wonderful people on #bootstrappable who are able to help
you work through ugly details
-Jeremiah
anyway)
So you'll have to clone https://github.com/oriansj/bootstrap-seeds if you want
a generated 357byte hex0 binary
- Jeremiah
to mention:
major enhancements to kaem thanks to fosslinux
Reproducible friendly tarball generation thanks to Janneke
Andrius Štikonas fixing a lot of my typos
-Jeremiah
> We are pleased to announce the release of GNU Mes 0.22, representing
> 57 commits over 8 weeks.
Great job as always Janneke, stage0's 0.3.0 release last week was far less
impressive.
-Jeremiah
once this piece is done we will have a full bootstrap from hex to GCC
https://github.com/oriansj/mes-m2
-Jeremiah
alternate null padding)
** Fixed
Fixed unsigned division in ARMv7l port
Fixed non-uniform behavior across locales and *BSDs
Fixed broken stack in ARMv7l thanks to dd
-Jeremiah
to decrypt /boot)
> The installer can and should be made to automatically amend the system
> config by mptspi etc.
To the examples, that would be fine but I have concerns about guix
silently fixing configuration files.
-Jeremiah
ines of code to try to
figureout how to deal with them.
-Jeremiah
/cryptsetup
Then I discover /dev/sda1 isn't even exist!!!
There is no documentation on how to mount and boot, let alone how to get
shepherd to prompt for credentials for the luks volume...
If nothing else we either need to include in the documentation how to
mount a luks volume and resume boot or ensure it works everytime.
-Jeremiah
> > Do you know where one can obtain a copy of this report? I did an
> > Internet search but couldn't find anything.
> me too
> Jeremiah: sorry if I insist (last time, promised!) but could you give us
> some more info about that report?
I am sorry for the delay, the
y on the
planet to deal with the risks written in the Nexus Intruder Report
published in 1958.
I could spend literal weeks ranting and raving about modern hardware
makes correctness impossible for all but the trivial or the so isolated
from the hardware that performance makes it a non-starter for anything
but journal articles which are never read and forgotten within a
generation.
-Jeremiah
in this
> line of work, and that's fine.
It isn't so much as not interested but rather it is lower on my priorities
> I appreciate the work you're doing > nonetheless.
As I appreciate the work you do as well.
-Jeremiah
n-free Businesses like
CompCert.
I'd love to see someone do it, I'd even throw in a few dollars into a
pot to fund it but it is so low down on my list of priorities, I'm not
going to be touching it in the next 2 decades...
-Jeremiah
internal
state and running only software explicitly specified and required for
the build.
Random system spot checks and wipes.
In short anything that makes single point compromises worthless needs to
be actively considered.
> Does that make sense?
Yes and hopefully my perspective makes sense as well.
-Jeremiah
can do this better. I look forward to more ideas and suggestions
from you on this subject later ^_^
Just an open reminder our #bootstrappable channel is always looking for
people intersted in these sorts of topics and we love hearing about what
you have created in this regard.
-Jeremiah
t; some links to the relevant bibliography?
I'll see if I can dig those up for you.
> so, having the scientific proof that binary conforms to source, there
> will be noo need to trust (the untrastable)
Well, that is what someone else could do with it but not a direct goal
of the work.
-Jeremiah
for those Intelligence Agencies but also ensure
Cyberwarfare against the Countries they work for that much more
effective.
Now that isn't to say they consider that an extranality and doom us all
but nothing stays hidden when we can read the source and can DDC our
entire bootstrap across arbitrary hardware/operating system
combinations.
-Jeremiah
king together will make us all a
dream that is too hard to achieve alone but easy now that we have each
other helping us all strive to a brighter future.
-Jeremiah
trivial:
https://github.com/oriansj/talk-notes/blob/master/Current%20bootstrap%20map.dot
)
> Jeremiah Orians is
> working to remove any need for mescc-tools-seed (esp. the forward
> dependency on Mes) but I don't think we're there yet.
We have eliminated the forward dependency on Mes for the
cking software.
-Jeremiah
the good of the project.
There are multiple details we will need to hammer out over time but the
general idea is we stop trying to force people who are different from
contributing in a positive manner.
-Jeremiah
y C compiler you like or bootstrap it from
stage0 https://savannah.nongnu.org/projects/stage0/
-Jeremiah
nux%20Bootstrap/hex0.hex
It was written one function at a time, with the arguments passed in registers
and careful preservation of everything passed.
- Jeremiah Orians
to finish the MesCC bootstrap from M2-Planet and then we
will have a complete bootstrap path from 250byte hex0 all the way up to
gcc ^_^
-Jeremiah Orians
ther plans imposed on my schedule.
Ricardo, we love you dearly but please for the love of all that is holy;
Get back to that vacation! *cracks whip* Burnout is a real thing and believe me
when I say bootstrapping is a marathon
Jeremiah Orians
Cell phone: (517) 896-2948
atforms will be able
to build the binary seeds for all of the other platforms with bit for bit
identical results (Which eliminates hardware based Trusting Trust attacks
avoiding detection)
Jeremiah Orians
Cell phone: (517) 896-2948
bridge to full bootstrappability
But we still have a lot of details to hammer out, like getting basic ARM
support and having the ARM and x86 binaries verify each other's bootstrap;
Finding 6502, z80, 8051, 68K, VAX, pdp11, Alpha, MIPS, SPARC and PowerPC/Power
Developer(s) to do stage0 work for their platforms and perform the cross verify
steps.
Hammer out cross-platform build details for MesCC and M2-Planet
Jeremiah Orians
Cell phone: (517) 896-2948
enerally what you'd expect for a compiler optimized for bootstrapping bigger
compilers
-Jeremiah
Cell phone: (517) 896-2948
On Signal and Riot
Today I proud to announce M2-Planet version 0.2.0
https://github.com/oriansj/M2-Planet
The world's simplest C compiler with support for:
structs with sizeof support
anonymous unions (inside of structs)
arrays
Inline assembly
Gotos
for, while and do loops with optional breaks bitshifting bitwise o
Today I proud to announce M2-Planet version 0.2.0
https://github.com/oriansj/M2-Planet
The world's simplest C compiler with support for:
structs with sizeof support
anonymous unions (inside of structs)
arrays
Inline assembly
Gotos
for, while and do loops with optional breaks
bitshifting
bitwise ope
> I am pleased to announce the release of Mes 0.15, representing 45 commits
> over 3 weeks. The GNU toolchain is getting bootstrapped!
Great work as always Janneke
-Jeremiah
As running make clean breaks the bootstrap script.
I propose we leverage git's shallow clones (git clone --depth 1 $URL)
and include the .git directory with the repo such that we could simply
have make clean check for git and if it exists run git clean -xdf and
then only if git fails to exist, fall
Amazing work as always Janneke
- Jeremiah Orians
> Jan is correct that Guile is still heavily tied to its C code. It's true
> that Guile's compiler is written in Scheme and that
> the C evaluator is used only during bootstrapping, but the C bootstrap
> evaluator is only a small piece of libguile.
> The majority of libguile is still needed. N
> Plus there is another angle on this. MesCC, the bootstrap C compiler in
> Scheme, is not a intended to be used beyond bootstrapping.
And probably will lose features over time not directly related to the act of
bootstrapping itself
> A C compiler on top of Guile however, could be a very inter
> It wouldn’t really help in that mescc+/guilecc is just as capable as the
> earlier mescc, no?
There is however a real difference in terms of performance, guile is simply
faster
> Indeed, Guile needs a C compiler.
Technically, it could be built from a lisp compiler
> In general, we need a C co
> Yeah, the mean reason to do it in Guix packages is that it becomes impossible
> to cheat. However, coding the bootstrap path in Guix
> means that we depend on some form of Guile...hmm.
Easy to break, simply allow each piece to be able to be built using only a
trivial shell script
> Now that MesCC starts to build TinyCC that starts to pass a large set of the
> mescc C tests, it's time to get walking the bootstrap path.
> Attached*) is my initial attempt for the full source bootstrap path in
> GuixSD; to try it, do
Very nicely done Janneke
>The starti
always love people who take time to make things
better.
-Jeremiah
ut a hex monitor or hex assembler, stage0-vm
downstrapping, MES tinycc bootstrapping, MES lisp bootstrapping, etc)
but ultimately shifting sands are the only grounds we can be certain
will be there.
So we better get comfortable minimizing our assumptions.
-Jeremiah
56 matches
Mail list logo
