[polly] Add diagnostic remark for ReportVariantBasePtr
Andreas Simbuerger
simbuerg at fim.uni-passau.de
Thu Jun 26 06:38:55 PDT 2014
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
At the moment the DebugLoc is derived from the BaseValue.
I'm not 100% sure if the resulting DebugLoc corresponds to the
A or the (A->b) BaseValue.
As far as I can tell, both would map to the same source location in
the debug-metadata.
Cheers,
Andreas
On 06/26/2014 02:32 PM, Tobias Grosser wrote:
> On 26/06/2014 13:54, Andreas Simbuerger wrote:
>> This adds a diagnostic remark for variant base pointers found
>> inside loops.
>>
>> Question: I'm not sure how to enhance the precision of the
>> diagnostic remark because the debug information gathered in the
>> test case is very limited. Has someone an idea how to generate &
>> find debug info that delivers more precise information than
>> 'somewhere in this assignment'?
>
> Very nice. I like such kind of incremental/small patches.
>
> To my understanding there should be debug info on the base pointer
> that gives you the name of the Pointer 'A' (not by looking at the
> LLVM-IR name, but the name in the original source code).
>
> You might also be able to find column infos, but that may not
> always be available.
>
> It already looks good to me, but if you feel like extending the
> precision of this, you are very much invited to do so.
>
> Cheers, Tobias
>
- --
Andreas Simbürger
University of Passau - Programming Group
http://www.infosun.fim.uni-passau.de/cl/staff/simbuerger/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBAgAGBQJTrCJvAAoJELS7a/6Ti2HY/GkH/jKALKfuCqaoN6u2DfkvL8ox
IOe2VJbngQVJbqlZIDN3q5WWo4uxJQQSydrHXiXEuh85uPx7VSGCGpcx4KGYGAB0
xltuaUWGpkuJDB3A/SGB5v2xJAvzoOT1JIihQr3khk0YS7O5mFkFMYyXTOxB6nCE
elo+F2Ybv/PXyqLZbXxMEMft/DUIgM+YioLSneyXM2IsvO+dOYQcvmXWZqPWVCHB
8ZvZiv2rz1qR3ODASAEd3SIXBFNQkeu7Kjv5a3u+RhnvVLsJ+drl4waMAakt6IOJ
Rfi/pj0pS568ra9MNZKCaws+VuMmZViu+3jHnyQDzti0M1wCkDHES5Ao9L03k2s=
=auUv
-----END PGP SIGNATURE-----
More information about the llvm-commits
mailing list