123200+ entries in 0.069s
phf: there was nothing "censored", it's just what was published are abstracts. litereally just reading corresponding AIMs will show you
that you can't literally rebuild
the cpu from
them
phf: scheme-79 is not "whole
thing published", which is something
that i said in
the logs multiple
times also.
there's AI memoes of variying detali, but
the actual
toolset, something called daedalus, and
the corresponding daedalus files
that actually describe
the chip, are nowhere
to be found. also dies will not be particularly interesting because
the whole point of daedalus was semi assisted layout
caaddr: perhaps one day we'll be able
to hang up a poster of
the
transistors
that caused
the FDIV bug
caaddr: that chip was about
the same era. it's certainly doable, but a chore unless you have significant passion for
the subject
caaddr: I enjoyed
the long series of posts where a gentleman reverse engineered
the 6502 die photograph, drawing
the schematic from
the photo
caaddr: but AIM-559 has
the details
caaddr: "WARNING: MAY STILL CONTAIN DANGEROUS LEVELS OF SANITY". yes, just a joke. it would be nice
to handle
them as an exercise in hardware archaeology
☟︎ caaddr: probably locked in a drawer somewhere, lest
the world learn from
them
caaddr: I
think I remember from
the paper
that only
two of
the actual pressed irons even worked. I wonder what happened
to
them?
caaddr: for now just remember: cdr
twice,
then car
twice. anybody else is an impostor ;)
caaddr: so I'll hold out for
trinque.
thank you
diana_coman: if it's not
that
the
trouble here
too,
trinque might help
a111: Logged on 2017-10-05 18:54
trinque: apeloyee: gpg: BAD04B14A4545828FABCE63C3DB30625393C0BB1: skipped: unusable public key << gpg has
this
to say about your fp
caaddr: compared
to compilation as a *software
transformation device*, which I consider a different case:
that is for automating levers, not running your program off of a cliff faster
than before
☟︎ caaddr: I suppose you would prefer hardware-only optimizations in any case, so ideally
they would not be part of
the software stack at all. compilation for performance as caching only
caaddr: I wonder how early in such a stack you would add
the kind of compile
time protections
that ada guarantees. compile
time protections seem
to be
the hardest
thing
to keep a programming language at "fits in head" size
caaddr: it would be nice
to bootstrap an entire operating system from machine code
to forth
to some strange mix of forth and ada, ada,
then
tinyscheme, and finally a sane common lisp subset
caaddr: Ken
Thompson hack ahoy
caaddr: oh, I remember
the gnat ouroboros from
the logs now
caaddr: it didn't, but I
thought source would be available
caaddr: I get
the same output with "!!up caaddr"
caaddr: I said "!!up"
to deedbot in pm, and it replied "You must be registered."
diana_coman: caaddr, say here steps + failure when you
tried
to !!up yourself
caaddr: GNATMAKE 4.9.2 is
the answer
to
the now redundant question. I'll use adacore instead. I had avoided
this because it contains precompiled binaries, with no independent reproducible build certification
☟︎ diana_coman: from my own experience with adacore and with gnat, I
tend
to agree with asciilifeform's evaluation
there ^^
diana_coman: caaddr, you should be able
to voice yourself from now on
diana_coman: caaddr, register a key please so we know it's you next
time
caaddr: yes, I created a vpatch. I'm happy
to add my key
to deedbot
too
caaddr: thanks, sorry about
that
diana_coman: upload
the patches
there + discussion as
to why and what; link
to asciilifeform's ch1 ffa and you're done
diana_coman: I suppose asciilifeform will want
to have a look at
them perhaps ; I'm not sure
though I see a point in changing ffa
to fit whatever gnat4 wants
though
shinohai: I believe mod6
told ne he got it running on deb, I haven't
tried
caaddr: so I've created a vpatch for both of
these issues, which makes
the genesis Chapter 1 code work with gnat-4
diana_coman: aha;
tbh you are best off using adacore's
tools
a111: Logged on 2017-11-23 17:55 whaack: asciilifeform: gnat1: error: unrecognized command line option ‘-fdump-scos’ when I
try gprbuild. gnat version 4.6 gcc version 4.8.4. I removed
the command line option from
the gpr file since it seemed
to be just used for coverage
tools.
Then got error prefix of "Image" attribute must be a
type in 3 places in blocks.adb
caaddr: having browsed
the logs of #trilema I've found
that I'm not
the only one who has run into issues:
caaddr: I'm
trying
to follow
the instructions precisely, and
that has included not using gcc-5.x or above. I'm just using
the standard gnat-4 package in debian which is linked
to
the gcc-4 package, and I've noticed
these are a bit out of date
caaddr: I've been working on Chapter 1 of
the ffalib guide
☟︎ shinohai: "hick-ups" <<< Is
this supposed
to be
the bumpkin version of "hiccough" ?
diana_coman: I really can't begin
to understand what exactly is
that; some gems in
there
too with organisation making silk-purse out of a sow's ear and "every participant has
the option
to be
that player" and ...
☟︎ mircea_popescu: reover,
the pretense
to
the contrary and
the "blank mind" humanist wank is strictly
the path
to insanity.
mircea_popescu: "Coping with radical novelty requires an orthogonal method. One must consider one's own past,
the experiences collected, and
the habits formed in it as an unfortunate accident of history, and one has
to approach
the radical novelty with a blank mind, consciously refusing
to
try
to link it with what is already familiar, because
the familiar is hopelessly inadequate." <<
this never was, and absolutely never will be
the case. mo
mircea_popescu: for
the record,
that dijkstra piece on "radical" bla bla is so fucking idiotic...
trinque: beyond "well and
then it worked"
trinque: it's been a great exercise, since
the histfile demands rationale.
trinque: I am not putting a negative in
the history file
a111: Logged on 2018-01-21 23:56 spyked looked at
the patch. admits
to not being able
to compile an example with gcc 4.9 nor 5; so
there's probably more
to it, e.g. C++ voodoo. I'm curious of asciilifeform's answer
mod6: <+mircea_popescu> iirc it just edits something in /etc/security/limits.conf ? << off
the
top of my head,
that's only like 50% of it.
there is at least one other
thing
that needs
to be set/configured
too.
a111: Logged on 2018-01-21 23:26 douchebag:
Thanks man, I've been spending a lot of my
time focusing on security research and helping others get involved in
the InfoSec community. I have a pretty decent resume compared
to most people I go
to college with because I have a pretty decent amount of experience, and when it comes
to InfoSec jobs experience is probably
the most important factor for most employers
mod6: I don't have
the incantation in front of me at
the moment... but if you would like it, I can dig it up for you
tomorrow.
mod6: <+hanbot> no onboard ulimit, no package found, heh. << it is a huge pain
to get a ulimit set on
these mclinux boxes. but after seriously, a bunch of
trial and error, I was able
to get it
to work.
a111: 2017-10-06 <Framedragger> yes but someone committing
to
the project without having
the necessary
time is not far away from malice, imho
trinque: though iirc Framedragger was lost into
that one never
to be seen again
a111: Logged on 2018-01-21 23:04 douchebag: Does anyone else in
this chat into web application pentesting?
mircea_popescu: asciilifeform
trinque you'd be surprised how many of
these exist!
trinque: if
that doesn't work
try 100000000 and so on