Displaying 2 results from an estimated 2 matches for "r289468".
Did you mean:
r279468
2016 Dec 12
1
Libfuzzer depending on uninitialized debug info
...tions not to emit any .loc directives;
done in r289256, plus r289288
(3) file a bug to have someone audit LoopVectorizer.cpp to see whether it is using SetCurrentDebugLocation in the right places;
haven't done that part yet
(4) reapply my "line 0" patch, which will be the 3rd attempt.
r289468
Please ping me when you do (4).
Also, will there be a flag to disable this new functionality?
I've make '-use-unknown-locations' into a 3-way option, you can do `-use-unknown-locations=Disable` to turn off emitting these line-0 records.
--paulr
From: Kostya Serebryany [mailto:kcc at...
2016 Dec 03
0
Libfuzzer depending on uninitialized debug info
On Fri, Dec 2, 2016 at 5:42 PM, Robinson, Paul <paul.robinson at sony.com>
wrote:
> I've determined that the "pesky" .loc is indeed because of the .cfi
> directive that comes immediately after it. Some of the CFI instructions
> have source locations, some don't. But, emitting a source location for a
> CFI instruction is inappropriate. It's easy enough to