Displaying 6 results from an estimated 6 matches for "mca_code_regions".
2018 Nov 15
2
[RFC][llvm-mca] Adding binary support to llvm-mca.
...vsd %xmm1, -16(%rbp)
.Lmca_code_region_start_0: # LLVM-MCA-START ID: 42
xorps %xmm0, %xmm0
movsd %xmm0, -24(%rbp)
movsd -8(%rbp), %xmm0
mulsd -16(%rbp), %xmm0
addsd -24(%rbp), %xmm0
movsd %xmm0, -24(%rbp)
.Lmca_code_region_end_0: # LLVM-MCA-END ID: 42
movsd -24(%rbp), %xmm0
popq %rbp
retq
.section .mca_code_regions,"", at progbits
.quad 42
.quad .Lmca_code_region_start_0
.quad .Lmca_code_region_end_0-.Lmca_code_region_start_0
The assembly has been trimmed to show the portions relevant to this RFC.
Notice the labels enclose the user's defined region, and that they preserve the
user's arbitra...
2018 Nov 21
2
[RFC][llvm-mca] Adding binary support to llvm-mca.
...bp)
> > movsd -8(%rbp), %xmm0
> > mulsd -16(%rbp), %xmm0
> > addsd -24(%rbp), %xmm0
> > movsd %xmm0, -24(%rbp)
> > .Lmca_code_region_end_0: # LLVM-MCA-END ID: 42
> > movsd -24(%rbp), %xmm0
> > popq %rbp
> > retq
> > .section .mca_code_regions,"", at progbits
> > .quad 42
> > .quad .Lmca_code_region_start_0
> > .quad .Lmca_code_region_end_0-.Lmca_code_region_start_0
> >
> > The assembly has been trimmed to show the portions relevant to this RFC.
> > Notice the labels enclose the user...
2018 Nov 27
2
[RFC][llvm-mca] Adding binary support to llvm-mca.
...direction of this RFC.
However, I am interesting to hear from other developers about your
suggested design.
> This initial patch only targets ELF object files, and does not handle
relocatable addresses. Since the start of a code region is represented as an
assembly label, and referenced in the .mca_code_regions section, that
address
is relocatable.
This may be okay for now. However, it would be nice to remove that
constraint in future and add support to generic object files.
-Andrea
On Thu, Nov 22, 2018 at 7:21 PM <Matthew.Davis at sony.com> wrote:
> I want to clarify a few restrictions of ll...
2018 Dec 03
2
[RFC][llvm-mca] Adding binary support to llvm-mca.
...om other developers about your
> > suggested design.
> >
> > > This initial patch only targets ELF object files, and does not handle
> > relocatable addresses. Since the start of a code region is represented as
> > an
> > assembly label, and referenced in the .mca_code_regions section, that
> > address
> > is relocatable.
> >
> > This may be okay for now. However, it would be nice to remove that
> > constraint in future and add support to generic object files.
> >
> > -Andrea
> >
> > On Thu, Nov 22, 2018 at 7:21 PM &l...
2018 Dec 10
4
[RFC][llvm-mca] Adding binary support to llvm-mca.
...> This initial patch only targets ELF object files, and does not
>>>> handle
>>>>>> relocatable addresses. Since the start of a code region is
>>>> represented as
>>>>>> an
>>>>>> assembly label, and referenced in the .mca_code_regions section, that
>>>>>> address
>>>>>> is relocatable.
>>>>>>
>>>>>> This may be okay for now. However, it would be nice to remove that
>>>>>> constraint in future and add support to generic object files.
>>...
2018 Dec 10
2
[RFC][llvm-mca] Adding binary support to llvm-mca.
...> > >
>> > > > This initial patch only targets ELF object files, and does not
>> handle
>> > > relocatable addresses. Since the start of a code region is
>> represented as
>> > > an
>> > > assembly label, and referenced in the .mca_code_regions section, that
>> > > address
>> > > is relocatable.
>> > >
>> > > This may be okay for now. However, it would be nice to remove that
>> > > constraint in future and add support to generic object files.
>> > >
>> > >...