in the past when we've grown these dependencies, it's blow the size limits out of the water so we've done other things to work around them. How much does this add to boot2? And what happens with gcc (either in-tree or out-of-tree) or old-clang when this is brought in? Listing it as a .o means it's always included in the binary output adding too the size.

this whole chunk is orthogonal.

But same questions about size. how much does this affect the size? For a .a it's less of a big deal to include too much because the loader won't pull in .o's from the .a it doesn't need.

In either case, I'd do this change separately.

Old clang output w/ ashldi3:

-rw-r--r--  1 root  wheel   3088 Aug 16 08:29 ashldi3.o
-rwxr-xr-x  1 root  wheel  38216 Aug 16 09:07 boot2.out

Without:

-rwxr-xr-x  1 root  wheel  37068 Aug 16 09:09 boot2.out

"kind of" orthogonal... there's conflicts between filenames in lib/libc/quad and compiler-rt; the former have qdivrem dependencies, the latter don't. We need to make sure we don't accidentally get lib/libc/quad versions.

boot2 has to fit in 7.5k... 38k is way beyond that... but there's headers and symbols there.

So can you give 'size' output?

We can make this change without the change to boot2, and it is applicable to today's compilers.

Whoops, sorry.

Pre-ashldi3:

text   data    bss     dec      hex   filename
5197     12   5273   10482   0x28f2   /usr/obj/usr/home/kevans/dev/base/head/amd64.amd64/stand/i386/boot2/boot2.out

Post-ashldi3:

text   data    bss     dec      hex   filename
5197     12   5273   10482   0x28f2   /usr/obj/usr/home/kevans/dev/base/head/amd64.amd64/stand/i386/boot2/boot2.out