[LLVMbugs] [Bug 686] NEW: llvmc configuration enhancements

bugzilla-daemon at cs.uiuc.edu bugzilla-daemon at cs.uiuc.edu
Mon Jan 9 00:17:17 PST 2006


http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=686

           Summary: llvmc configuration enhancements
           Product: tools
           Version: trunk
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: llvmc
        AssignedTo: rspencer at x10sys.com
        ReportedBy: rspencer at x10sys.com


We want llvmc to be more configurable by including target-specific as well as
language-specific configuration information. Additionally, the configuration
data needs to be compiled in by default so we're not always reading a whole
bunch of text files on every llvmc invocation. That said, the config files need
to be retained as well as allowing compiled dynamic loading of the configuration
information.

Consequently, the following enhancements to llvmc regarding its configuration
are requested:

1. Enhance llvmc to handle target-specific configuration data as well. Target
   triples should be used to identify the platform/machine. The configuration 
   data for targets would specify things like native linker and assembler 
   command line invocation options for a variety of tasks. 

2. Create a set of C++ classes to represent the configuration of the driver.
   These classes must provide constructors that utilize strings or enums so that
   it is possible to create a highly readable configuration file in C++.

3. Compile in a set of instances of the C++ configuration classes (#1) as the
   standard configuration that supports known languages and targets.

4. Allow dynamic libraries of those config classes to be loaded at runtime via a 
   command line option to specify either a file or a directory full of files. 
   This allows non-supported or experimental targets and languages to have their
   own compiled configuration module to go along with the target or language's
   extension to LLVM.

5. Allow a textual representation of the configurations to be parsed that
   converts the text into corresponding C++ object instances that are merged in
   with other configuration data provided. Text file configuration is specified
   with command line argument.

6. Allow an object representation of configuration data to print itself in the
   textual format. Use this to permit reproduction of llvmc's configuration data
   in a human readable format.

7. Consider making the entire configuration mechanism a separate library or a
   support utility rather than placing it in llvmc directly.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




More information about the llvm-bugs mailing list