Displaying 20 results from an estimated 20000 matches similar to: "[LLVMdev] asm parser functionality"
2013 Nov 12
1
[LLVMdev] asm parser functionality
Right now inline assembler just passes through to the assembler if there
is no direct object emitter.
If there is a direct object emitter, it gets processed in Asm parser and
MC instructions are produced.
I propose that the initial parsing happen very early and the inline
assembly code be replaced with a sequence of MachineInstructions in the
basic block where it occurs.
Then code like
2013 Nov 12
0
[LLVMdev] asm parser functionality
A more concrete proposal would be good. I have no idea what you think
you mean by this.
-eric
On Tue, Nov 12, 2013 at 12:48 PM, reed kotler <rkotler at mips.com> wrote:
> It seems that some parts of asm parser should be moved earlier into llvm.
>
> It should be possible to parse inline assembler and produce a list of
> machine instructions that can be merged into the normal
2013 Feb 17
2
[LLVMdev] pseudo lowering
On Feb 17, 2013, at 1:01 PM, Reed Kotler <rkotler at mips.com> wrote:
> On 02/17/2013 12:48 PM, Andrew Trick wrote:
>> On Feb 16, 2013, at 1:31 PM, Cameron Zwarich <zwarich at apple.com> wrote:
>>
>>> That's exactly the right place.
>> Really? You don't want the expansion to be optimized? You want to specify a machine model for the pseudo's
2014 Jan 29
3
[LLVMdev] making emitInlineAsm protected
On 01/28/2014 06:29 PM, Eric Christopher wrote:
> Uhhhh...
>
> -eric
>
> On Tue, Jan 28, 2014 at 4:56 PM, reed kotler <rkotler at mips.com> wrote:
>> I would like to make the following member of AsmPrinter be protected
>>
>>
>> void EmitInlineAsm(StringRef Str, const MDNode *LocMDNode = 0,
>> InlineAsm::AsmDialect
2013 Feb 17
0
[LLVMdev] pseudo lowering
On 02/17/2013 01:08 PM, Andrew Trick wrote:
>
> On Feb 17, 2013, at 1:01 PM, Reed Kotler <rkotler at mips.com
> <mailto:rkotler at mips.com>> wrote:
>
>> On 02/17/2013 12:48 PM, Andrew Trick wrote:
>>> On Feb 16, 2013, at 1:31 PM, Cameron Zwarich<zwarich at apple.com> wrote:
>>>
>>>> That's exactly the right place.
2013 Feb 17
4
[LLVMdev] pseudo lowering
On Feb 16, 2013, at 1:31 PM, Cameron Zwarich <zwarich at apple.com> wrote:
> That's exactly the right place.
Really? You don't want the expansion to be optimized? You want to specify a machine model for the pseudo's as if they're real instructions? You don't want to schedule or register allocate the real instructions?
-Andy
> On Feb 16, 2013, at 1:08 PM, Reed
2014 Jan 29
6
[LLVMdev] making emitInlineAsm protected
I would like to make the following member of AsmPrinter be protected
void EmitInlineAsm(StringRef Str, const MDNode *LocMDNode = 0,
InlineAsm::AsmDialect AsmDialect =
InlineAsm::AD_ATT) const;
I have some stubs that I want to emit in MipsAsmParser .
Are there any objections to doing this?
Reed
2013 Feb 17
4
[LLVMdev] keeping instructions in order and hidden dependencies
You are trying to do a few different things here, and a uniform solution may not work for all of them. For a fixed instruction sequence, e.g. a special kind of move-and-branch sequence used for tail calls, you probably want a pseudo. If you are trying to combine arbitrary instructions together, e.g. Thumb IT blocks, you probably want to use bundles, even if the sequences are a fixed length. I
2013 Feb 17
0
[LLVMdev] pseudo lowering
On 02/17/2013 12:48 PM, Andrew Trick wrote:
> On Feb 16, 2013, at 1:31 PM, Cameron Zwarich <zwarich at apple.com> wrote:
>
>> That's exactly the right place.
> Really? You don't want the expansion to be optimized? You want to specify a machine model for the pseudo's as if they're real instructions? You don't want to schedule or register allocate the real
2015 Mar 19
2
[LLVMdev] Final added to parser<bool>
One could argue that mclinker is doing something good or not by how it's using this class
but I don't see the need for parser<bool> to be final. That is a subjective opinion that mclinker needs to
be changed.
I think that "final" was added to some of these command line classes to avoid some kind of clang warning.
That seems wrong to me that the tools are dictating
2015 Mar 19
2
[LLVMdev] Final added to parser<bool>
//===----------------------------------------------------------------------===//
// FalseParser
//===----------------------------------------------------------------------===//
class FalseParser : public parser<bool> {
public:
explicit FalseParser(Option &O) : parser<bool>(O) { }
// parse - Return true on error.
bool parse(cl::Option& O, StringRef ArgName, StringRef
2015 Mar 19
3
[LLVMdev] Final added to parser<bool>
On 03/19/2015 08:55 AM, David Blaikie wrote:
>
>
> On Thu, Mar 19, 2015 at 4:30 AM, Reed Kotler <Reed.Kotler at imgtec.com
> <mailto:Reed.Kotler at imgtec.com>> wrote:
>
> One could argue that mclinker is doing something good or not by
> how it's using this class
> but I don't see the need for parser<bool> to be final. That is a
>
2015 Mar 19
4
[LLVMdev] Final added to parser<bool>
Well, you are an mclinker contributor and Google uses mclinker and now
it's broken as the result of your change.
I still don't see any justification to making a change in a public
interface that is used by other non LLVM projects
to fix some issue with clang warnings. People should be able to derive
from those classes. I can't understand
your reasoning as to why these classes must
2013 Nov 23
2
[LLVMdev] bugpoint question
In that case it tries to do something but fails.
rkotler at ubuntu-rkotler:~/testmips16$
/home/rkotler/llvmw/install/bin/bugpoint casts.bc -llc-safe
--safe-tool-args -target=mips-linux-gnu -mcpu=mips16
-mips16-constant-islands
Read input file : 'casts.bc'
*** All input ok
Initializing execution environment: Found llc:
/home/rkotler/llvmw/install/bin/llc
Running the code
2015 Mar 19
2
[LLVMdev] Final added to parser<bool>
Hi David,
Is there a reason that we need to have "final" for parser<bool> ???
This breaks the compilation of mclinker which derives a class from this.
In file included from
/home/rkotler/workspace/mclinker/lib/Support/CommandLine.cpp:9:0:
/home/rkotler/workspace/mclinker/include/mcld/Support/CommandLine.h:49:7: error:
cannot derive from ‘final’ base
2015 Mar 19
2
[LLVMdev] Final added to parser<bool>
On 03/19/2015 09:24 AM, David Blaikie wrote:
>
>
> On Thu, Mar 19, 2015 at 9:18 AM, Reed Kotler <reed.kotler at imgtec.com
> <mailto:reed.kotler at imgtec.com>> wrote:
>
> Well, you are an mclinker contributor
>
>
> Me personally? Not that I know of.
Sorry. I thought i had seen your name in an mclinker commit.
>
> and Google uses mclinker
>
2015 Mar 19
2
[LLVMdev] Final added to parser<bool>
On 03/19/2015 09:38 AM, David Blaikie wrote:
>
>
> On Thu, Mar 19, 2015 at 9:34 AM, Reed Kotler <reed.kotler at imgtec.com
> <mailto:reed.kotler at imgtec.com>> wrote:
>
> On 03/19/2015 09:24 AM, David Blaikie wrote:
>>
>>
>> On Thu, Mar 19, 2015 at 9:18 AM, Reed Kotler
>> <reed.kotler at imgtec.com <mailto:reed.kotler at
2013 Apr 19
1
[LLVMdev] funny llvm bug
On Fri, Apr 19, 2013 at 1:50 PM, Reed Kotler <rkotler at mips.com> wrote:
> On 04/19/2013 12:43 PM, Joerg Sonnenberger wrote:
>>
>> On Fri, Apr 19, 2013 at 09:47:28AM -0700, reed kotler wrote:
>>>
>>> The clean solution is probably to add two additional function
>>> attributes to cover these additional pieces, namely "ax" and
>>>
2015 Mar 19
2
[LLVMdev] Final added to parser<bool>
On 03/19/2015 09:57 AM, David Blaikie wrote:
>
>
> On Thu, Mar 19, 2015 at 9:52 AM, Reed Kotler <reed.kotler at imgtec.com
> <mailto:reed.kotler at imgtec.com>> wrote:
>
> On 03/19/2015 09:38 AM, David Blaikie wrote:
>>
>>
>> On Thu, Mar 19, 2015 at 9:34 AM, Reed Kotler
>> <reed.kotler at imgtec.com <mailto:reed.kotler at
2013 Nov 23
2
[LLVMdev] bugpoint question
This is my first time using bugpoint. I'm getting the following error:
/home/rkotler/llvmw/install/bin/bugpoint -run-llc casts.bc --tool-args
-target mips-linux-gnu -mcpu=mips16 -mips16-constant-islands
Read input file : 'casts.bc'
*** All input ok
Initializing execution environment: Found llc:
/home/rkotler/llvmw/install/bin/llc
Sorry, I can't automatically select a