r211844 - Add test coverage for .bc input in the frontend

CCing in llvmdev..

The only test coverage for this feature is CodeGen/X86/GC/ocaml-gc.ll where it contains an equally unhelpful value:

-; CHECK-NEXT: .file "<stdin>"

So I agree, it looks like this is breaking an invariant in the compilation pipeline by causing us to not generate identical output from identical inputs. Also like an information leak to emit file paths on the build system when they weren't requested.

If it's been wrong and untested so long, might it be best to just remove the feature? If needed, a new IL name could be added as an explicit feature later on, but the current approach of forcing the module name to be embedded in output seems flawed.

--- a/lib/CodeGen/AsmPrinter/AsmPrinter.cpp
+++ b/lib/CodeGen/AsmPrinter/AsmPrinter.cpp
@@ -199,13 +199,6 @@ bool AsmPrinter::doInitialization(Module &M) {
    // Allow the target to emit any magic that it wants at the start of the file.

- // Very minimal debug info. It is ignored if we emit actual debug info. If we
- // don't, this at least helps the user find where a global came from.
- if (MAI->hasSingleParameterDotFile()) {
- // .file "foo.c"
- OutStreamer.EmitFileDirective(M.getModuleIdentifier());
- }