Displaying 6 results from an estimated 6 matches for "mca_code_region".
Did you mean:
mca_code_regions
2018 Nov 15
2
[RFC][llvm-mca] Adding binary support to llvm-mca.
...; form the region that can be analyzed by llvm-mca at a
later time.
Example
-----------
Before we go into the details of this proposed change, let's first look at a
simple example:
// example.c -- Analyze a dot-product expression.
double test(double x, double y) {
double result = 0.0;
__mca_code_region_start(42);
result += x * y;
__mca_code_region_end();
return result;
}
In the example above, we have identified a code region, in this case a single
dot-product expression. For the sake of brevity and simplicity, we've chosen
a very simple example, but in reality a more complicated exa...
2018 Nov 21
2
[RFC][llvm-mca] Adding binary support to llvm-mca.
...ke
such a case will probably not produce an expected result for the user.
We could introduce a warning, or automatically divide the regions so
that a single region can only contain a single block.
> My understanding is that code regions are not allowed to overlap. So, it
> makes sense if ` __mca_code_region_end()` doesn't take an ID as input.
> However, what if ` __mca_code_region_end()` ends in a different basic block?
>
> `__mca_code_region_start()` has to always dominate `
> __mca_code_region_end()`. This is trivial to verify when both calls are in
> a same basic block; however,...
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 l...
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 &...
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.
>&g...
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.
>> > >
>> > >...