Displaying 4 results from an estimated 4 matches for "bentura".
Did you mean:
ventura
2015 Jul 07
2
[LLVMdev] ARM Jump table pcrelative relaxation in clang / llc
...{ nounwind }
!llvm.module.flags = !{!0, !1, !2}
!llvm.ident = !{!3}
!0 = !{i32 1, !"wchar_size", i32 4}
!1 = !{i32 1, !"min_enum_size", i32 4}
!2 = !{i32 1, !"PIC Level", i32 1}
!3 = !{!"clang version 3.7.0 (trunk 229364)"}
2015-07-06 21:13 GMT+03:00 Eric Bentura <ebentura at gmail.com>:
> It is certainly helping - Thanks Renato.
>
> 2015-07-06 18:39 GMT+03:00 Renato Golin <renato.golin at linaro.org>:
>
>> On 6 July 2015 at 16:32, Eric Bentura <ebentura at gmail.com> wrote:
>> > I tried to build the object file...
2015 Jul 06
3
[LLVMdev] ARM Jump table pcrelative relaxation in clang / llc
...g even with -filetype=obj. The transformation I apply are in
the optimizer so I must build the new bc to create the object file.
Thanks for your help
Eric
Le dimanche 5 juillet 2015, Tim Northover <t.p.northover at gmail.com> a
écrit :
> Hi Eric,
>
> On 5 July 2015 at 07:22, Eric Bentura <ebentura at gmail.com> wrote:
> > As a result it seems that the generated machine code is incorrect (as of
> > LLVM 3.5): The AsmPrinter generates the following instruction :
> > adr r2, .LJTI4_0_0
> > when going through the MC streamer, I get a "fatal error: err...
2015 Jul 13
2
[LLVMdev] ARM Jump table pcrelative relaxation in clang / llc
...mbler.getBackend().mayNeedRelaxation(Inst)) {
EmitInstToData(Inst, STI);
return;
}
At this stage, the instruction as been already selected to be ARM::ADR.
The call to mayNeed
2015-07-07 18:06 GMT+03:00 Tim Northover <t.p.northover at gmail.com>:
> On 7 July 2015 at 06:06, Eric Bentura <ebentura at gmail.com> wrote:
> > I have created a small ll file to reproduce the problem.
> > I used the intrinsic function llvm.arm.space to introduce space between
> the
> > beginning of the code and the jump table.
>
> It does look like the value in @llvm.arm.s...
2015 Jul 05
2
[LLVMdev] ARM Jump table pcrelative relaxation in clang / llc
Hi,
I have written a PassManager (IR) pass that seriously increases the size of
the original IR code.
As a result it seems that the generated machine code is incorrect (as of
LLVM 3.5): The AsmPrinter generates the following instruction :
adr r2, .LJTI4_0_0
when going through the MC streamer, I get a "fatal error: error in backend:
out of range pc-relative fixup" .
Apparently, the fixup