"-Os might cause compiler bugs on sh3" comment was for egcs or gcc3.
"-Os" might be also safe, but use the same one with the default sh3 build
for now.
Briefly tested on (not emulated but real) dreamcast.
really be autogenerated, but seems it's generally not required by
stuff in rump and guessing the location of the appropriate genassym.cf
is difficult without a major consultation.
Thanks to Havard for spotting the build failure.
the System Use field with fewer then 28 bytes to spare, we were
remembering the wrong length for the System Use field and hence
emitting a corrupt directory entry. This could be triggered by trying
to build a filesystem containing a regular file with a 120-byte name.
Now we're a little more careful.
Continuation Area, be sure to insert the "CE" record at the correct
point in the chain of SUSP records. Without this, makefs emits
an invalid image if any file needs a Continuation Area. The bug
seems to have been introduced with the conversion to TAILQs.
without supplying a value, complain at them instead of segfaulting.
Or, to put it another way, check that the value is non-NULL before calling
set_option().
Ignore '=' and ' ' inside {} and () when looking for an assignment operator.
Also require the operator be immediately after any whitespace.
XXX mismatched (){} in variable modifiers will not DTRT.
symbol namespace. This has several implications:
* no symbols are accidentally linked against host platform libraries
* all host platform access is done via rumpuser, and hence the
portability of rump is now well defined
* functionality such as proplib can now exist within the rump virtual
kernel and the application using it
Thanks to uwe for originally suggesting the bulk renaming approach
over a pint of what I believe was very crisp, curious and untypical
stout. It had an almost acidic characteristic with fruity notes
and lacking dark and roasted flavours.
And thanks to lukem for pointing me in the right direction with make.
disk_read_sector() wants DEV_BLKSIZE blkno's BUT sectorsize unit lengths
specified... how `logical'.
Real fixup pending on discussion on tech-kern/source-changes.
Explicitly pass a pointer to the kernel lock/unlock routines in
rumpuser init instead of magically relying on the linker giving us
the symbols.
thanks to uwe for pointing out
- Use device_t and cfdata_t rather than explicit structure pointers.
- Use device_private() rather than a cast to convert device_t to a softc.
- Use device_*() to get at the innards of device_t.
device/softc split not done yet because of worrying about bootstrap console
stuff.
- Split device_t out of softc.
- Use device_t and cfdata_t rather than explicit structure pointers.
- Use device_*() rather than accessing parts of device_t directly.
- Use aprint_*() rather than printf().
Also ANSIfy arcpppushbytes.
sucks in all libkern sources), so mark them ".hidden". I'm not sure
if this is the best course of action (dropping millicode from librump
might be a better idea), but it's the quickest fix to get sh3 builds
going again for now.
