search for: mordekoviz

Displaying 8 results from an estimated 8 matches for "mordekoviz".

2018 Aug 08
2
Passing arguments to var args function
...his example is only one of a few I can think of for expanding the CallingConvention tablegen capabilities regarding this issue. Thanks for the answer. On Wed, Aug 8, 2018 at 4:21 PM, Tim Northover <t.p.northover at gmail.com> wrote: > Hi Liad, > > On Wed, 8 Aug 2018 at 13:28, Liad Mordekoviz via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > Did anyone else come by such requirement? is there any other way anyone > could recommend handling such requirement? > > Apple's calling convention on iOS does this. We have two separate > CC_Whatever definitions...
2017 Dec 14
0
Help adding entries to .symtab
...he reference to be fixed up as part of the normal assembly and linking process, nothing special there. It's a little more complicated if the two instructions are in different compilation units, but if they are in the same compilation then it should be pretty straightforward. --paulr From: Liad Mordekoviz [mailto:liad.mordekoviz at nextsilicon.com] Sent: Thursday, December 14, 2017 1:00 PM To: Robinson, Paul; llvm-dev Subject: Re: [llvm-dev] Help adding entries to .symtab Hey Paul, first of all thank you for taking the time to answer me, if I understand you correctly, I need to modify the instructi...
2017 Dec 14
2
Help adding entries to .symtab
...cution. If you need to change the instruction itself, for example to > have the instruction refer to memory somewhere, then you need to modify the > instruction itself. > > --paulr > > > > *From:* llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] *On Behalf Of *Liad > Mordekoviz via llvm-dev > *Sent:* Thursday, December 14, 2017 2:37 AM > *To:* llvm-dev > *Subject:* [llvm-dev] Help adding entries to .symtab > > > > Hi everyone, > > > > I am fairly new to LLVM, I'm working on a new backend. > > I am trying to add information to a s...
2018 Aug 08
2
Passing arguments to var args function
Hey, I am working on a new back-end, in my back end, I require to pass every argument through a register when calling a function, unless the argument is part of the ellipsis (...) and then pass it through the stack, I've tried creating a CCCustom function to analyze the operands when a function has var args, however, the information whether the out val is fixed or not is not passed into the
2017 Dec 14
2
Help adding entries to .symtab
Hi everyone, I am fairly new to LLVM, I'm working on a new backend. I am trying to add information to a specific instruction using the .symtab in the ELF format. I've been searching through the LLVM source code trying to find a way to do such a thing. Can anyone help me with some directions or point me to some documents in the matter. Thanks, Liad. -------------- next part --------------
2018 Jan 21
1
Splitting BB pre SelectionDAG
Hi everyone, I'm faily new to LLVM, I'm working on a new backend. In my backend, one of the requirements is to split a BB on every call, I considered putting some kind of pseudo instruction using the TargetLowering::LowerCall function. Before going said path, I was wondering if there is some way to split the BB before the SelectionDAG is generated, this way the call instruction would be
2018 Feb 27
0
Repo directory layout
..., things are likely to move around. The second layout is more flexible because it doesn't put any repo inside another repo, so I would recommend adopting it. At the very least, using it will put you in a good position to adapt to any future layout changes. On Mon, Feb 19, 2018 at 1:36 AM Liad Mordekoviz via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hey all, > There seems to be two conventions for git repo directory layout. > The official docs suggest the following tree. > http://llvm.org/docs/GettingStarted.html#git-mirror > > llvm (llvm repo) > -> tools >...
2018 Feb 19
2
Repo directory layout
Hey all, There seems to be two conventions for git repo directory layout. The official docs suggest the following tree. http://llvm.org/docs/GettingStarted.html#git-mirror llvm (llvm repo) -> tools -> clang (clang repo) -> lld (lld repo) etc. However various llvm-project repos, suggest a different layout: https://github.com/llvm-project/llvm-project-20170507