Displaying 20 results from an estimated 32 matches for "djordj".
Did you mean:
djordje
2019 Sep 11
3
Dwarf - 5 features in clang and llvm
Hello Djordje, Vedant,
Thanks a lot for sharing information.
I have a doubt, please consider the following simple test case-
#include <iostream>
int func(int* ptr){
std::cout << *ptr;
return *ptr + 5;
}
int main(int argc, char** argv){
int a = 4;
int* ptr_a = &a...
2020 Feb 20
2
[LLVM][DISubprogram][LL format updation query] Question regarding moving DISubprogram DIFlags to DISPFlag.
...ecks the presence of SPFlags to see if the definition is present in bool or spflag if I move flags to spflags, it will create problems hence some of the flags may be present in spflags and in Boolean, as in example spFlags: DISPFlagThunk, isLocal: True.
- Chirag.
-----Original Message-----
From: Djordje Todorovic <djordje.todorovic at rt-rk.com>
Sent: 20 February 2020 14:40
To: Chirag Patel <Chirag at raincode.com>; llvm-dev at lists.llvm.org
Subject: Re: [llvm-dev] [LLVM][DISubprogram][LL format updation query] Question regarding moving DISubprogram DIFlags to DISPFlag.
Hi Chirag,...
2019 Sep 10
2
Dwarf - 5 features in clang and llvm
> On Sep 10, 2019, at 6:15 AM, Djordje Todorovic via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
> Hi Sourabh,
>
> Support for call-site related DWARF 5 tag/attributes is implemented very late, in the LLVM middle-end.
> Please note that there is also the IR-level flag (DIFlagAllCallsDescribed) that lowers to
&...
2020 Jun 18
2
[DebugInfo] RFC: Introduce LLVM DI Checker utility
...t why not
start with something simple? -check-debugify already knows how to report
when & where a location is dropped, it would be simple to teach it to
emit a report when a variable is fully optimized-out.
I agree. We can do that and that could be used from both utilities.
Best regards,
Djordje
On 17.6.20. 21:14, Vedant Kumar wrote:
> Hey Djordje,
>
> It looks like a lot of the new infrastructure introduced here
> <https://github.com/djolertrk/llvm-di-checker/commit/9d26ac2557c584f6cf82ac5535fc47f8bd267a27> consists
> of logic copied from the debugify implementat...
2020 Feb 20
3
[LLVM][DISubprogram][LL format updation query] Question regarding moving DISubprogram DIFlags to DISPFlag.
...ant to remove it and update the all the ll files which still uses it.
Also the metadata read will support old format, no changes in that.
so if ll file has isLocal and isDefinition it will result in parser error. But the bitcode read will work as usual.
- Chirag.
-----Original Message-----
From: Djordje Todorovic <djordje.todorovic at rt-rk.com>
Sent: 20 February 2020 14:16
To: Chirag Patel <Chirag at raincode.com>; llvm-dev at lists.llvm.org
Subject: Re: [llvm-dev] [LLVM][DISubprogram][LL format updation query] Question regarding moving DISubprogram DIFlags to DISPFlag.
Hi Chirag,...
2020 Sep 09
2
[RFC] [DebugInfo] Using DW_OP_entry_value within LLVM IR
Hi Djordje,
On Wed, Sep 9, 2020 at 7:52 AM Djordje Todorovic
<Djordje.Todorovic at syrmia.com> wrote:
> Using entry-values ('callee' side of the feature) is not enough in any case. It is always connected to the call-site-param (function arguments but we call it call-site-params; 'caller...
2020 Sep 01
2
[RFC] [DebugInfo] Using DW_OP_entry_value within LLVM IR
...e DBG_VALUE_LIST will be appropriate for the "Salvage Debug Info", but the idea of using the entry values on IR level is more general (not very localized), and there is the cause of potential complexity, since we need to carry that info throughout IR and use it as a backup.
Best regards,
Djordje
________________________________
From: David Stenberg <david.stenberg at ericsson.com>
Sent: Tuesday, September 1, 2020 11:38 AM
To: Djordje Todorovic <Djordje.Todorovic at syrmia.com>; llvm-dev at lists.llvm.org <llvm-dev at lists.llvm.org>
Cc: paul.robinson at sony.com <paul...
2020 Feb 10
2
Enabling debug entry value production by default
...how tuning-controlled features are supposed to work. I will comment on the review.
I see, I am working on addressing the comments from the [1]. I will update the diff asap. Thanks.
Vedant,
There are no entry values generated at -O0 level, but I will add a test case for it. Thanks.
Best regards,
Djordje
On 8.2.20. 02:41, Robinson, Paul via llvm-dev wrote:
> This is not how tuning-controlled features are supposed to work. I will comment on the review.
>
> --paulr
>
>
>
> *From:* vsk at apple.com <vsk at apple.com> *On Behalf Of * Vedant Kumar
> *Sent:* Friday,...
2020 Sep 01
4
[RFC] [DebugInfo] Using DW_OP_entry_value within LLVM IR
...// DIEntryValExpression implicitly contains DW_OP_entry_value operation
The bottom line is that the production of call-site side of the feature stays the same, but LLVM will have more freedom to generate more of DW_OP_entry_values operation on the callee side.
Any thoughts on this?
Best regards,
Djordje
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200901/266dde12/attachment.html>
2013 May 26
1
load ff object in a different computer
...o luck.
In addition, when I open the .ffData file to see what is inside, there is
only a path to the ff1a831... temporary file. As information about ff
package in internet is rather scarce, could anyome please help me to
understand this, and possibly recover my data if it is possible?
Thank you!
Djordje
[[alternative HTML version deleted]]
2020 Jun 17
4
[DebugInfo] RFC: Introduce LLVM DI Checker utility
...the utility
like this could be useful when trying to detect the real issues related
to debug info production by the compiler.
Any thoughts on this? Thanks in advance!
[0] https://github.com/djolertrk/llvm-di-checker
[1] https://djolertrk.github.io/di-checker-html-report-example/
Best regards,
Djordje
2020 Feb 07
4
Enabling debug entry value production by default
..., constants, etc. to work out what was passed to the callee. There's a nice write-up about the impact of this feature in [3]. A big thank you to all of contributors who've helped us get here (I've tried to CC everyone, sincere apologies if I've accidentally left you out).
I believe Djordje and I have shown that there isn't an outsized binary size or compile time impact of enabling this feature. The aggregate size of DWARF in a stage2 x86_64 RelWithDebInfo clang build grows by under 0.2%, and we didn't find a significant compile time impact. We've shared CTMark results (b...
2019 Dec 23
2
[INFO] Buildbot llvm-docs failure
Hi all,
It looks like the llvm-sphinx-docs fails for a long time (at least 20 days).
Can someone please confirm if this is true?
Best regards,
Djordje
2020 Sep 08
2
[RFC] [DebugInfo] Using DW_OP_entry_value within LLVM IR
Hi Djordje,
[Late reply as I was away, alas],
For the example in https://reviews.llvm.org/D85012 , I'm not sure that
just using an entry value is correct. The reason why the dbg.values
for arguments are set to undef is not because the value can't be
described, it's because deadargelim changes a...
2020 Feb 07
2
Enabling debug entry value production by default
...s, etc. to work out what was passed to the callee. There's a nice write-up about the impact of this feature in [3]. A big thank you to all of contributors who've helped us get here (I've tried to CC everyone, sincere apologies if I've accidentally left you out).
>
> I believe Djordje and I have shown that there isn't an outsized binary size or compile time impact of enabling this feature. The aggregate size of DWARF in a stage2 x86_64 RelWithDebInfo clang build grows by under 0.2%, and we didn't find a significant compile time impact. We've shared CTMark results (b...
2019 Sep 10
2
Dwarf - 5 features in clang and llvm
Hello All,
I was working on some dwarf-5 features and debugging optimized code support
in clang and llvm.
Noticed that, DW_TAG_call_site is supported in llvm middle-end. but clang
is not emitting these.
I was hoping, if someone could provide current status of these features and
current status of dwarf-5 features in clang and llvm.
That will be immensely helpful.
Thanks!
Sourabh.
--------------
2020 Feb 07
2
Enabling debug entry value production by default
..., etc. to work out what was passed to the callee. There's a nice write-up about the impact of this feature in [3]. A big thank you to all of contributors who've helped us get here (I've tried to CC everyone, sincere apologies if I've accidentally left you out).
>
> I believe Djordje and I have shown that there isn't an outsized binary size or compile time impact of enabling this feature. The aggregate size of DWARF in a stage2 x86_64 RelWithDebInfo clang build grows by under 0.2%, and we didn't find a significant compile time impact. We've shared CTMark results (b...
2020 Jan 14
2
DebugInfo: Purpose of call site tags
...he design discussion in
https://reviews.llvm.org/D72489:
Me (Blaikie): I'm not sure why AT_call_return_pc would be needed at a tail
call site as the debugger must ignore it. As for emitting DW_AT_low_pc
under gdb tuning, I think this might be an artifact from the original GNU
implementation.
Djordje: Yes, that is the GNU implementation's heritage (I cannot remember
why GCC generated the low_pc info in the case of the tail calls), but GNU
GDB needs the low_pc (as an address) in order to handle the call_site and
call_site_parameters debug info for non-tail calls. To avoiding the pc
address...
2009 Mar 31
1
summarize logical string
...from
0 1 1 1 0 0 0 0 1 1 0 1 0 0
this: 1 3 4 2 1 1 2
so a string that gives me the number of repeated values, no matter zeros
or ones.
I've been diving in the manuals and the mailing list but, nothing
interesting, apparently... I would be very grateful if anyone could give
me some advice.
Djordje Bajic
Logic of Genomic Systems Lab
Centro Nacional De Biotecnolog?a - CSIC
Cantoblanco, Madrid, Espa?a
2019 Nov 15
2
Commit history duplicated, seeing weird diffusion activity (Was: [Diffusion] rG67c416dc9a5a: [DebugInfo] Allow spill slots in call site parameter descriptions)
...nel.
>
> This reverts commit eb4c98ca3d2590bad9f6542afbf3a7824d2b53fa (
> [DebugInfo] Exclude memory location values as parameter entry values),
> effectively reintroducing the portion of D60716 <https://reviews.llvm.org/D60716> which dealt with memory
> locations (authored by Djordje, Nikola, Ananth, and Ivan).
>
> This partially addresses llvm.org/PR43343. However, not all memory
> operands forwarded to callees live in spill slots. In the xnu build, it
> may be possible to use an escape analysis to increase the number of call
> site parameter by another 15% (m...