OK, I got it. Just a simple gimple_call_internal_p.
Shuai
On Tue, Jun 9, 2020 at 4:31 PM Shuai Wang wrote:
> Hello,
>
> All right, now I know how to print out GIMPLE internal functions. I do the
> following and it won't crash:
>
> const gcall* a = as_a (stmt);
>
Hello,
All right, now I know how to print out GIMPLE internal functions. I do the
following and it won't crash:
const gcall* a = as_a (stmt);
const char * tt =
internal_fn_name(gimple_call_internal_fn(a));
However, just a follow-up question, how can I a
Dear Richard,
Thank you for the information. Yes, that makes sense to me.
Nevertheless, is there any chance that I can still pinpoint this special
function call? Currently I can iterate all GIMPLE call statements, but how
to exactly figure out ASAN_MARK seems quite obscure.
Thank you!
Best,
Shu
On Tue, Jun 9, 2020 at 3:38 AM Shuai Wang via Gcc wrote:
>
> Hello!
>
> I am writing to report a potential bug I encountered when playing with the
> GIMPLE IR. I enabled the ASan and would like to print out all ASAN_MARK
> statements for the following simple code:
>
> int main(int argc ,char **ar
