Displaying 3 results from an estimated 3 matches for "pr20787".
2014 Oct 22
2
[LLVMdev] RFC: Are we ready to completely move away from the optionality of a DataLayout?
On Wed Oct 22 2014 at 12:33:53 PM Chris Lattner <clattner at apple.com> wrote:
> On Oct 20, 2014, at 10:41 PM, Eric Christopher <echristo at gmail.com> wrote:
> >>> So the storage for DataLayout right now is on a per-subtarget basis.
> >>> I.e. if you don't construct one in the module the backend will make
> >>> one up based on information in
2014 Oct 23
2
[LLVMdev] Target specific info available to Clang (and others)
So,
In order to fix bug PR20787 (common parsing infrastructure for FPU
options between LLVM and tools), I need to create a parser in LLVM
that has all targets' information (types of fpus, cpus, archs, etc)
but that can also be visible by external tools.
Until now, all that information has been hidden from view by creating
th...
2014 Oct 25
2
[LLVMdev] [cfe-dev] Target specific info available to Clang (and others)
On 24 Oct 2014, at 18:17, Renato Golin <renato.golin at linaro.org> wrote:
> I'm beginning to think that the "nice" feature 1 is not worth the two
> big problems 2 and 3. If we tie Clang builds with back-end builds and
> force it not to have support for other arches (because the info isn't
> available if you don't build its back-end), than all that info can