From 31fec98c2a3399e1397dbe0944f52892842c55d0 Mon Sep 17 00:00:00 2001
From: Daniel Dunbar
Date: Sat, 17 Oct 2009 22:08:19 +0000
Subject: [PATCH] Describe/link some of the universal driver related work.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@84369 91177308-0d34-0410-b5e6-96231b3b80d8
---
www/UniversalDriver.html | 32 ++++++++++++++++++++++++++++++++
1 file changed, 32 insertions(+)
diff --git a/www/UniversalDriver.html b/www/UniversalDriver.html
index 16f8bb6cf9..ff79901041 100644
--- a/www/UniversalDriver.html
+++ b/www/UniversalDriver.html
@@ -47,6 +47,38 @@ welcome!
See also PR4127.
+Existing Solutions and Related Work
+
+
+ - gcc's command line arguments -V, -B, -b are
+ generic but limited solutions to related problems. Similarly, -m32
+ and -m64 solve a small subset of the problem for specific
+ architectures.
+
+ - gcc's multilibs
+ solve the part of the problem that relates to finding appropriate libraries
+ and include files based on particular feature support (soft float,
+ etc.).
+
+ - Apple's "driver driver" supported by gcc and clang solve a subset of the
+ problem by supporting -arch. Apple also provides a tool chain which
+ supports universal
+ binaries and object files which may include data for multiple
+ architectures. See TN2137
+ for an example of how this is used.
+
+ - Many operating systems and environments solve the problem by installing
+ complete development environments (including the IDE, tools, header files,
+ and libraries) for a single tool chain. This is cumbersome for users and
+ does not match well with tools which are inherently capable of cross
+ compiling.
+
+ - The Debian ArmEabiPort
+ wiki page for their work to support the ARM EABI provide an interesting
+ glimpse into how related issues impact the operating system distribution.
+
+
+