You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At least in some situations, the database can wind up with a Type with no size, even though that Type is for a typedef whose underlying type has a known size. This caused bad IR generation, although that was fixable by always using the size of the unspecified type.
To repro, run the following query on the LGTM database for g/nlohmann/json:
See github#8805 for the underlying issue. The symptom was bad IR generation on a large number of functions because we never generated an `IRVariable` for a parameter with the affected type.
At least in some situations, the database can wind up with a
Typewith no size, even though thatTypeis for atypedefwhose underlying type has a known size. This caused bad IR generation, although that was fixable by always using the size of the unspecified type.To repro, run the following query on the LGTM database for g/nlohmann/json:
Expected Result:
No results
Actual Result:
~871 types for which there is no size, despite the unspecified type having a size
I was unable to come up with a small repro in a QL test, so it might be tricky to debug.
The text was updated successfully, but these errors were encountered: