search for: fct2_instk

Displaying 6 results from an estimated 6 matches for "fct2_instk".

Did you mean: fct2_inst1
2013 Oct 30
0
[LLVMdev] Preserving accurate stack traces with optimization?
...nlining. E.g., what do you expect from code like this: static void fct1(…) { ... } static void fct2(…) { … fct1(…) ... } void fct3(…) { fct1(...) … fct2(…) … } Assuming everything is inlined in fct3, you get: void fct3(…) { …. 1. fct1_inst1… fct1_instN …. 2. fct2_inst1… fct2_instK 3. fct1_inst1… fct1_instN 4. fct2_instzK+1… fct2_instN ... } Does it mean you what something like this each point of interest for you stack frame: 1. #0 fct1 #1 fct3 2. #0 fct2 #1 fct3 3. #0 fct1 #1 fct2 #2 fct3 4. #0 fct2 #1 fct3 Cheers, -Quentin On Oct 28, 2013, at 2:56 PM, Philip Re...
2013 Oct 30
2
[LLVMdev] Preserving accurate stack traces with optimization?
...atic void fct2(…) { > … > fct1(…) > ... > } > > void fct3(…) { > fct1(...) > … > fct2(…) > … > } > > Assuming everything is inlined in fct3, you get: > void fct3(…) { > …. > 1. fct1_inst1… fct1_instN > …. > 2. fct2_inst1… fct2_instK > 3. fct1_inst1… fct1_instN > 4. fct2_instzK+1… fct2_instN > ... > } > > Does it mean you what something like this each point of interest for > you stack frame: > 1. > #0 fct1 > #1 fct3 > > 2. > #0 fct2 > #1 fct3 > > 3. > #0 fct1 > #1 fc...
2013 Oct 30
0
[LLVMdev] Preserving accurate stack traces with optimization?
...; } >> >> void fct3(…) { >> fct1(...) >> … >> fct2(…) >> … >> } >> >> Assuming everything is inlined in fct3, you get: >> void fct3(…) { >> …. >> 1. fct1_inst1… fct1_instN >> …. >> 2. fct2_inst1… fct2_instK >> 3. fct1_inst1… fct1_instN >> 4. fct2_instzK+1… fct2_instN >> ... >> } >> >> Does it mean you what something like this each point of interest for you stack frame: >> 1. >> #0 fct1 >> #1 fct3 >> >> 2. >> #0 fct2 >&...
2013 Oct 28
3
[LLVMdev] Preserving accurate stack traces with optimization?
Is there a known way to preserve a full and accurate stack trace while utilizing most of LLVM's optimization abilities? We are investigating using LLVM as a JIT for a language which requires the ability to generate an accurate stack trace from any arbitrary point(1) during the execution. I know that we can make this work by doing inlining externally, manually recording virtual frames,
2013 Oct 30
2
[LLVMdev] Preserving accurate stack traces with optimization?
...ic void fct2(…) { > … > fct1(…) > ... > } > > void fct3(…) { > fct1(...) > … > fct2(…) > … > } > > Assuming everything is inlined in fct3, you get: > void fct3(…) { > …. > 1. fct1_inst1… fct1_instN > …. > 2. fct2_inst1… fct2_instK > 3. fct1_inst1… fct1_instN > 4. fct2_instzK+1… fct2_instN > ... > } > > Does it mean you what something like this each point of interest for you > stack frame: > 1. > #0 fct1 > #1 fct3 > > 2. > #0 fct2 > #1 fct3 > > 3. > #0 fct1 > #...
2013 Oct 31
0
[LLVMdev] Preserving accurate stack traces with optimization?
...;>> fct2(…) >>> … >>> } >>> >>> Assuming everything is inlined in fct3, you get: >>> void fct3(…) { >>> …. >>> 1. fct1_inst1… fct1_instN >>> …. >>> 2. fct2_inst1… fct2_instK >>> 3. fct1_inst1… fct1_instN >>> 4. fct2_instzK+1… fct2_instN >>> ... >>> } >>> >>> Does it mean you what something like this each point of interest >>> for you stack frame: >>> 1. >>&g...