Displaying 6 results from an estimated 6 matches for "stavrakantonaki".
2015 Dec 15
4
Line number without -Debug ?
...uot;no" as there's
> nothing for anything to retrieve. Diagnostics inside the compiler can
> usually get it from certain IR constructs that have line information,
> but I'm not sure if that's what you mean.
>
> -eric
>
> On Mon, Dec 14, 2015 at 5:54 PM Irini Stavrakantonaki via llvm-dev
> <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
>
> Hi list,
>
> Is it possible to retrieve the source/IR line number
> without being on a debug mode?
>
> Thank you in advance,
>
> --
> irin...
2015 Oct 16
2
Break nested instructions?
On 16/10/15 12:59, David Chisnall wrote:
> On 16 Oct 2015, at 10:44, Irini Stavrakantonaki via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>> Following call instruction contains a GEP instruction as its first operand
> No it doesn’t. It contains a GEP constant expression. This is a bit confusing at first, especially when working with IRBuilder, which can sometimes give...
2015 Oct 16
3
Break nested instructions?
Is there any pass that breaks an expression out of an instruction's
operand into its own instruction, so that such nested instructions
become explicit and are thus easier to work with in?
e.g Following|call|instruction contains a|GEP|instruction as its first
operand. Is there any pass which allows me to break up this:
| %call = call i32 (i8*, ...)* @printf(i8* getelementptr inbounds ([4
2015 Dec 15
2
Line number without -Debug ?
Hi list,
Is it possible to retrieve the source/IR line number
without being on a debug mode?
Thank you in advance,
--
irini
2015 Oct 16
2
Break nested instructions?
On 16/10/15 14:09, mats petersson wrote:
> I think it's important to understand that this is not ALWAYS the case.
> The operands can be either a constant expression or an instruction.
>
> For example:
>
> char *a;
> int x;
>
> if(cond) a = "%d";
> else a = "%x";
> printf(a, x);
>
> In this case, the compiler
2015 Oct 16
2
Break nested instructions?
On 16/10/15 14:33, mats petersson wrote:
> Interesting point, I'm not sure - but the operand on an "instruction"
> is a Value, so I expect it can be any type that is within the Value
> class hierarchy?
I expected the same. That's why I was searching a way to "break" the
inlined instructions, as nested instructions are not convenient for me.
In case the