Displaying 13 results from an estimated 13 matches for "inl1".
Did you mean:
inl
2016 Dec 15
6
distinct DISubprograms hindering sharing inlined subprogram descriptions
...rked 'distinct', the
CU link would cause them to effectively be so) remain separate - this means
that inlined versions in one CU don't refer to an existing subprogram
definition in another CU.
To demonstrate:
inl.h:
void f1();
inline __attribute__((always_inline)) void f2() {
f1();
}
inl1.cpp:
#include "inl.h"
void c1() {
f2();
}
inl2.cpp:
#include "inl.h"
void c2() {
f2();
}
Compile to IR, llvm-link the result. The DWARF you get is basically the
same as the DWARF you'd get without linking:
DW_TAG_compile_unit
DW_AT_name "inl1.cpp"
DW_TAG_...
2016 Dec 15
1
distinct DISubprograms hindering sharing inlined subprogram descriptions
...te - this means
> that inlined versions in one CU don't refer to an existing subprogram
> definition in another CU.
> >
> > To demonstrate:
> > inl.h:
> > void f1();
> > inline __attribute__((always_inline)) void f2() {
> > f1();
> > }
> > inl1.cpp:
> > #include "inl.h"
> > void c1() {
> > f2();
> > }
> > inl2.cpp:
> > #include "inl.h"
> > void c2() {
> > f2();
> > }
> >
> > Compile to IR, llvm-link the result. The DWARF you get is basically the
>...
2016 Dec 15
0
distinct DISubprograms hindering sharing inlined subprogram descriptions
...ld cause them to effectively be so) remain separate - this means that inlined versions in one CU don't refer to an existing subprogram definition in another CU.
>
> To demonstrate:
> inl.h:
> void f1();
> inline __attribute__((always_inline)) void f2() {
> f1();
> }
> inl1.cpp:
> #include "inl.h"
> void c1() {
> f2();
> }
> inl2.cpp:
> #include "inl.h"
> void c2() {
> f2();
> }
>
> Compile to IR, llvm-link the result. The DWARF you get is basically the same as the DWARF you'd get without linking:
>
>...
2016 Dec 15
0
distinct DISubprograms hindering sharing inlined subprogram descriptions
...them to effectively be so) remain separate - this means
> that inlined versions in one CU don't refer to an existing subprogram
> definition in another CU.
>
> To demonstrate:
> inl.h:
> void f1();
> inline __attribute__((always_inline)) void f2() {
> f1();
> }
> inl1.cpp:
> #include "inl.h"
> void c1() {
> f2();
> }
> inl2.cpp:
> #include "inl.h"
> void c2() {
> f2();
> }
>
> Compile to IR, llvm-link the result. The DWARF you get is basically the
> same as the DWARF you'd get without linking:
>...
2016 Dec 15
2
distinct DISubprograms hindering sharing inlined subprogram descriptions
...them to effectively be so) remain separate - this means
> that inlined versions in one CU don't refer to an existing subprogram
> definition in another CU.
>
> To demonstrate:
> inl.h:
> void f1();
> inline __attribute__((always_inline)) void f2() {
> f1();
> }
> inl1.cpp:
> #include "inl.h"
> void c1() {
> f2();
> }
> inl2.cpp:
> #include "inl.h"
> void c2() {
> f2();
> }
>
> Compile to IR, llvm-link the result. The DWARF you get is basically the
> same as the DWARF you'd get without linking:
>...
2016 Dec 23
0
distinct DISubprograms hindering sharing inlined subprogram descriptions
...ld cause them to effectively be so) remain separate - this means that inlined versions in one CU don't refer to an existing subprogram definition in another CU.
>
> To demonstrate:
> inl.h:
> void f1();
> inline __attribute__((always_inline)) void f2() {
> f1();
> }
> inl1.cpp:
> #include "inl.h"
> void c1() {
> f2();
> }
> inl2.cpp:
> #include "inl.h"
> void c2() {
> f2();
> }
>
> Compile to IR, llvm-link the result. The DWARF you get is basically the same as the DWARF you'd get without linking:
>
>...
2016 Dec 15
0
distinct DISubprograms hindering sharing inlined subprogram descriptions
...te - this means
>> that inlined versions in one CU don't refer to an existing subprogram
>> definition in another CU.
>>
>> To demonstrate:
>> inl.h:
>> void f1();
>> inline __attribute__((always_inline)) void f2() {
>> f1();
>> }
>> inl1.cpp:
>> #include "inl.h"
>> void c1() {
>> f2();
>> }
>> inl2.cpp:
>> #include "inl.h"
>> void c2() {
>> f2();
>> }
>>
>> Compile to IR, llvm-link the result. The DWARF you get is basically the
>> same a...
2016 Dec 23
2
distinct DISubprograms hindering sharing inlined subprogram descriptions
...them to effectively be so) remain separate - this means
> that inlined versions in one CU don't refer to an existing subprogram
> definition in another CU.
>
> To demonstrate:
> inl.h:
> void f1();
> inline __attribute__((always_inline)) void f2() {
> f1();
> }
> inl1.cpp:
> #include "inl.h"
> void c1() {
> f2();
> }
> inl2.cpp:
> #include "inl.h"
> void c2() {
> f2();
> }
>
> Compile to IR, llvm-link the result. The DWARF you get is basically the
> same as the DWARF you'd get without linking:
>...
2016 Dec 24
0
distinct DISubprograms hindering sharing inlined subprogram descriptions
...that inlined versions in one CU don't refer to an existing subprogram definition in another CU.
>>>
>>> To demonstrate:
>>> inl.h:
>>> void f1();
>>> inline __attribute__((always_inline)) void f2() {
>>> f1();
>>> }
>>> inl1.cpp:
>>> #include "inl.h"
>>> void c1() {
>>> f2();
>>> }
>>> inl2.cpp:
>>> #include "inl.h"
>>> void c2() {
>>> f2();
>>> }
>>>
>>> Compile to IR, llvm-link the result. The D...
2016 Dec 15
2
distinct DISubprograms hindering sharing inlined subprogram descriptions
...rked 'distinct', the
CU link would cause them to effectively be so) remain separate - this means
that inlined versions in one CU don't refer to an existing subprogram
definition in another CU.
To demonstrate:
inl.h:
void f1();
inline __attribute__((always_inline)) void f2() {
f1();
}
inl1.cpp:
#include "inl.h"
void c1() {
f2();
}
inl2.cpp:
#include "inl.h"
void c2() {
f2();
}
Compile to IR, llvm-link the result. The DWARF you get is basically the
same as the DWARF you'd get without linking:
DW_TAG_compile_unit
DW_AT_name "inl1.cpp"
DW_TAG_...
2016 Dec 16
0
distinct DISubprograms hindering sharing inlined subprogram descriptions
...them to effectively be so) remain separate - this means
> that inlined versions in one CU don't refer to an existing subprogram
> definition in another CU.
>
> To demonstrate:
> inl.h:
> void f1();
> inline __attribute__((always_inline)) void f2() {
> f1();
> }
> inl1.cpp:
> #include "inl.h"
> void c1() {
> f2();
> }
> inl2.cpp:
> #include "inl.h"
> void c2() {
> f2();
> }
>
> Compile to IR, llvm-link the result. The DWARF you get is basically the
> same as the DWARF you'd get without linking:
>...
2016 Dec 16
2
distinct DISubprograms hindering sharing inlined subprogram descriptions
...them to effectively be so) remain separate - this means
> that inlined versions in one CU don't refer to an existing subprogram
> definition in another CU.
>
> To demonstrate:
> inl.h:
> void f1();
> inline __attribute__((always_inline)) void f2() {
> f1();
> }
> inl1.cpp:
> #include "inl.h"
> void c1() {
> f2();
> }
> inl2.cpp:
> #include "inl.h"
> void c2() {
> f2();
> }
>
> Compile to IR, llvm-link the result. The DWARF you get is basically the
> same as the DWARF you'd get without linking:
>...
2016 Dec 16
0
distinct DISubprograms hindering sharing inlined subprogram descriptions
...te - this means
>> that inlined versions in one CU don't refer to an existing subprogram
>> definition in another CU.
>>
>> To demonstrate:
>> inl.h:
>> void f1();
>> inline __attribute__((always_inline)) void f2() {
>> f1();
>> }
>> inl1.cpp:
>> #include "inl.h"
>> void c1() {
>> f2();
>> }
>> inl2.cpp:
>> #include "inl.h"
>> void c2() {
>> f2();
>> }
>>
>> Compile to IR, llvm-link the result. The DWARF you get is basically the
>> same a...