The bytecode is not a novel creative work and does not have a separate copyright, this affects, for example, copyright terms (not that they are already relevant

The bytecode is not a novel creative work and does not have a separate copyright, this affects, for example, copyright terms (not that they are already relevant for code with the terms being so long) - the effective copyright date is when you wrote the source code, not when it was compiled; and of course the authorship - it does not matter who owns the machine or who initiated the compiling, only the writing of the original source code. But it is protected effectively as a "copy in a different format" of the original work - just as for a book, perhaps the author originally wrote as a manuscript with a quill on parchment or on a computer, and for the physical printed book it matters when and how the book was originally written (first 'fixed on a durable medium'), not what machines or tools were used in typesetting and printing the copy that you have - and the printed copy is still protected as a copy of that original creative work fixed in a manuscript. In essence, as far as copyright law is concerned, the bytecode isn't generated by a tool, it's transformed by a tool.