https://sourceware.org/bugzilla/show_bug.cgi?id=31964
--- Comment #6 from Nick Clifton <nickc at redhat dot com> ---
(In reply to Jakub Jelinek from comment #5)
> 1) @command{uuencode} program's @code{-m} option
> I think base64 program from coreutils is more common than uuencode from
> sharutils,
> so either mention just that, or both. For no line wrapping base64 has -w
> 0 option.
That is a fair point. I will change the example to use the base64 program as
you suggested.
> 2) I don't know how FRAG_APPEND_1_CHAR is expensive compared to say
> appending more
It is actually pretty fast unless the specific backend involved needs to do
something funky.
> Just running coreutils base64 on 261M file
> took around 1s and base64 -d of that too.
I tried a similar test using /usr/bin/lto-dump (29Mb) and it took the assembler
less than a second to convert the base64 encoded version of the file into an
object file containing the binary.
--
You are receiving this mail because:
You are on the CC list for the bug.
