From 38551dfec1fbb0889b0e1e4dd395fdf2ffdd1279 Mon Sep 17 00:00:00 2001 From: Dominic Kempf Date: Mon, 9 Sep 2019 14:20:58 +0200 Subject: [PATCH] [bugfix] Do not treat the read_variables field of CInstruction as pymbolic It is expected to be an iterable of strings. Trying to build keys from it as if it was pymbolic results in raw strings ending up in the pymbolic mappers (being foreign objects). --- loopy/kernel/instruction.py | 2 -- 1 file changed, 2 deletions(-) diff --git a/loopy/kernel/instruction.py b/loopy/kernel/instruction.py index 9b5c7a5b4..8213c9584 100644 --- a/loopy/kernel/instruction.py +++ b/loopy/kernel/instruction.py @@ -1216,8 +1216,6 @@ class CInstruction(InstructionBase): set("iname_exprs code read_variables assignees".split()) pymbolic_fields = InstructionBase.pymbolic_fields | \ set("assignees".split()) - pymbolic_set_fields = InstructionBase.pymbolic_set_fields | \ - set(["read_variables"]) def __init__(self, iname_exprs, code, -- GitLab