kallisti5 added a comment.

No worries. I was wondering if this one would match llvm's goals.
Do you see any iteration of these changes that would be accepted? (not using 
define's, etc)

We currently support "hybrid" operating system builds where we compile a 
secondary toolchain / abi.

An current functional example of this is we offer a gcc2 compiler + support 
libraries, and then also offer a gcc7 compiler + support libraries.

  $ getarch
  x86_gcc2
  $ gcc --version
  ~gcc 2.95
  $ gcc test.c -o test
  $ ./test
  
  test is a functional binary generated by gcc2 and run using the gcc2 ABI + 
libraries.
  
  
  $ setarch x86
  $ getarch
  x86
  $ gcc --version
  ~gcc 7.3
  $ gcc test.c -o test
  $ ./test
  
  test is now a functional binary generated by gcc7 and run using the gcc7 
ABI's + libraries


Repository:
  rC Clang

https://reviews.llvm.org/D49480



_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
  • [PATCH] D49480: Hai... Alexander von Gluck IV via Phabricator via cfe-commits
    • [PATCH] D49480... Alexander von Gluck IV via Phabricator via cfe-commits
    • [PATCH] D49480... Joerg Sonnenberger via Phabricator via cfe-commits
    • [PATCH] D49480... Alexander von Gluck IV via Phabricator via cfe-commits

Reply via email to