Displaying 20 results from an estimated 9000 matches similar to: "[LLVMdev] DataLayout"
2014 Oct 21
2
[LLVMdev] RFC: Are we ready to completely move away from the optionality of a DataLayout?
On Mon, Oct 20, 2014 at 9:11 PM, Chris Lattner <clattner at apple.com> wrote:
>
> On Oct 20, 2014, at 8:22 PM, Eric Christopher <echristo at gmail.com> wrote:
>
>> On Mon, Oct 20, 2014 at 7:51 PM, Chris Lattner <clattner at apple.com> wrote:
>>> Hi Eric,
>>>
>>> Can you elaborate on your goals and what problem you are trying to solve? As
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 20
2
[LLVMdev] RFC: Are we ready to completely move away from the optionality of a DataLayout?
On Mon, Oct 20, 2014 at 1:27 PM, Chandler Carruth <chandlerc at google.com> wrote:
>
> On Mon, Oct 20, 2014 at 1:18 PM, Eric Christopher <echristo at google.com>
> wrote:
>>
>> Agreed. The DataLayout should move (back) to the TargetMachine and live
>> there (I'm doing that part right now). I don't particularly want to put it
>> on the module
2015 Mar 11
3
[LLVMdev] DataLayout: Module vs Target
Hi all,
The Language Reference says:
"The function of the data layout string may not be what you expect. Notably, this is not a specification from the frontend of what alignment the code generator should use.
Instead, if specified, the target data layout is required to match what the ultimate code generator expects. This string is used by the mid-level optimizers to improve code, and this
2014 Oct 20
2
[LLVMdev] RFC: Are we ready to completely move away from the optionality of a DataLayout?
On Mon, Oct 20, 2014 at 9:51 AM, Chris Lattner <clattner at apple.com> wrote:
>
> On Oct 19, 2014, at 1:22 AM, Chandler Carruth <chandlerc at gmail.com> wrote:
>
> > I've just wasted a day chasing my tail because of subtleties introduced
> to handle the optionality of the DataLayout. I would like to never do this
> again. =]
> >
> > We now have
2014 Oct 21
3
[LLVMdev] RFC: Are we ready to completely move away from the optionality of a DataLayout?
On Mon, Oct 20, 2014 at 7:51 PM, Chris Lattner <clattner at apple.com> wrote:
> Hi Eric,
>
> Can you elaborate on your goals and what problem you are trying to solve? As Chandler points out, DataLayout is part of module for a reason.
Which is an interesting point - it's not really. (This was also going
to be part of my talk next week, but since it's been brought up...)
So
2010 Jan 18
1
[LLVMdev] Finding the host datalayout
Hello all,
As we work the last few bugs out of our project for the last release, we need to find a way to set the default datalayout of the LLVM Assembly file we are generating to be that of the host machine. I've seen options for target triples in the Doxygen but not the datalayout. BTW, we're using version 2.6 of LLVM.
--Sam
2014 Apr 11
3
[LLVMdev] Advice on field access, adding a Modula-3 front end
I am doing some preliminary investigation into splicing the Modula-3
compiler front end onto llvm. I have a number of questions and will
no doubt have more, but will start by asking for advice on this one.
The M3 front end has lowered things farther than the llvm IR expects.
Whereas llvm accesses fields/data members of records/structs by field
number, M3 has already laid out the format of
2016 Sep 14
4
setDataLayout segfault
I get a segfault with this code when setting the data layout:
int main(int argc, char** argv)
{
llvm::InitializeNativeTarget();
llvm::LLVMContext TheContext;
unique_ptr<Module> Mod(new Module("A",TheContext));
llvm::EngineBuilder engineBuilder(std::move(Mod));
std::string mcjit_error;
engineBuilder.setMCPU(llvm::sys::getHostCPUName());
2016 Sep 14
2
setDataLayout segfault
Ok. I can make a copy of the unique_ptr before moving it into the
builder's constructor and use the copy later on. It is confusing to
require a unique_ptr.
Frank
On 09/14/2016 12:11 PM, Frank Winter via llvm-dev wrote:
> I am constructing the engine builder in the following way:
>
> llvm::SMDiagnostic Err;
> unique_ptr<Module> Mod = getLazyIRFileModule("f.ll",
2014 Oct 19
14
[LLVMdev] RFC: Are we ready to completely move away from the optionality of a DataLayout?
I've just wasted a day chasing my tail because of subtleties introduced to
handle the optionality of the DataLayout. I would like to never do this
again. =]
We now have this attached to the Module with just a flimsy faked-up pass to
keep APIs consistent. So, is there any problem with beginning down the path
of:
1) Synthesizing a "default" boring DataLayout for all modules that
2014 Aug 25
3
[LLVMdev] Module->getDataLayout returns std::string instead of DataLayout
hey,
so I'm writing in cpp.
the documentation says that TheModule -> getDataLayout should return
const DataLayout, but instead it is returning std::string.
I require it to return DataLayout, as I generalize my function
pass manager to accept the DataLayout constant as an argument, it
being the only thing in common amongst both the ExecutionEngine and
the Module class.
Any pointers to
2016 May 05
2
MCJIT - missing DataLayout?
Hi everyone,
I was happily using MCJIT for over a year until yesterday when I created a
function call with an argument of a struct type. That caused a crash in
SelectionDAG around DataLayout::getAlignment().
I remember the noise about the DataLayout started being mandatory. But I
cannot find precise information.
Should I set the DataLayout in every Module created?
Where can I get the
2016 Feb 19
3
target triple in 3.8
I added your suggestion and am using this now
llvm::legacy::FunctionPassManager *functionPassManager = new
llvm::legacy::FunctionPassManager(Mod);
llvm::PassRegistry ®istry = *llvm::PassRegistry::getPassRegistry();
initializeScalarOpts(registry);
functionPassManager->add( new
llvm::TargetLibraryInfoWrapperPass(llvm::TargetLibraryInfoImpl(targetMachine->getTargetTriple()))
);
2015 Jun 22
2
[LLVMdev] How to Obtain a DataLayout Reference Given a Function & F
I’ve been debugging SAFECode source code files, and line 170 in ArrayBoundCheckLocal.cpp has been causing the following compilation error:
In file included from /Users/peterfinn/Desktop/llvm_trunk_2/projects/safecode/lib/ArrayBoundChecks/ArrayBoundCheckLocal.cpp:18:
In file included from
2012 Apr 16
0
[LLVMdev] datalayout optimization question
Are you expecting to use a single set of IR files to generate code for multiple targets? Otherwise I'm not sure why your .ll files would necessarily lack the data layout information. The reason I ask is that LLVM IR is fundamentally not target independent in ways far beyond the presence or absence of the data layout string.
For gory details:
2012 Apr 16
3
[LLVMdev] datalayout optimization question
Hi all,
We are developing our own compiler front-end and use LLVM as back-end. We generate .ll files and use opt/llc to generate target specific code. When I generate datalayout information in my .ll file it seems that it enables more optimization from LLVM opt. How can I determine which optimization are driven by datalayout information generation ?
In other words, when I don't generate
2014 Oct 21
2
[LLVMdev] RFC: Are we ready to completely move away from the optionality of a DataLayout?
> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On
> Behalf Of Chris Lattner
> On Oct 20, 2014, at 8:22 PM, Eric Christopher <echristo at gmail.com> wrote:
>
> > On Mon, Oct 20, 2014 at 7:51 PM, Chris Lattner <clattner at apple.com>
> wrote:
> >> Hi Eric,
> >>
> >> Can you elaborate on your goals and what
2015 Feb 09
2
[LLVMdev] DataLayout missing in isDereferenceablePointer()
Hi,
I've been debugging this issue for many hours, and would like a sanity
check. The issue is that DL (DataLayout) is nullptr inside
isDereferenceablePointer() no matter what I try. Why is DataLayout
ever nullptr (shouldn't it get defaults?), and what should I do to
make it non-nullptr?
Thanks.
Ram
2014 Jan 30
4
[LLVMdev] make DataLayout a mandatory part of Module
On 29 January 2014 15:53, Jim Grosbach <grosbach at apple.com> wrote:
> Hi Nick,
>
> The main use case I’ve seen is that it makes writing generic test cases
> for ‘opt’ easier in that it’s not necessary to specify a target triple on
> the command line or have a data layout in the .ll/.bc file. That is, in my
> experience, it’s more for convenience and perhaps historical