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
I recently read the PLDI '23 paper on cut-shortcut and found it very inspiring. I’m currently working on pointer analysis for C programs. What attracts me most about cut-shortcut is its approach to improving context-sensitivity by handling merge flows.
However, since I’m not very familiar with Java programs, I’d like to ask: how prevalent is the use of merge flows in Java compared to C? My current understanding is that a large portion of merge flows comes from patterns like getter/setter methods and containers or other similar constructs. Are there any other field load/store patterns beyond getter/setter that contribute significantly to merge flows?
The purpose of this question is that I’d like to compare the characteristics of Java and C programs in this regard.
🐛 Current Behavior
Nan
🔄 Reproducible Example
No response
⚙️ Tai-e Arguments
🔍 Click here to see Tai-e Options
{{The content of 'output/options.yml' file}}
🔍 Click here to see Tai-e Analysis Plan
{{The content of 'output/tai-e-plan.yml' file}}
📜 Tai-e Log
🔍 Click here to see Tai-e Log
{{The content of 'output/tai-e.log' file}}
ℹ️ Additional Information
No response
The text was updated successfully, but these errors were encountered:
📝 Overall Description
Some question about PLDI'23 paper: cut-shortcut.
🎯 Expected Behavior
I recently read the PLDI '23 paper on cut-shortcut and found it very inspiring. I’m currently working on pointer analysis for C programs. What attracts me most about cut-shortcut is its approach to improving context-sensitivity by handling merge flows.
However, since I’m not very familiar with Java programs, I’d like to ask: how prevalent is the use of merge flows in Java compared to C? My current understanding is that a large portion of merge flows comes from patterns like getter/setter methods and containers or other similar constructs. Are there any other field load/store patterns beyond getter/setter that contribute significantly to merge flows?
The purpose of this question is that I’d like to compare the characteristics of Java and C programs in this regard.
🐛 Current Behavior
Nan
🔄 Reproducible Example
No response
⚙️ Tai-e Arguments
🔍 Click here to see Tai-e Options
{{The content of 'output/options.yml' file}}
🔍 Click here to see Tai-e Analysis Plan
{{The content of 'output/tai-e-plan.yml' file}}
📜 Tai-e Log
🔍 Click here to see Tai-e Log
ℹ️ Additional Information
No response
The text was updated successfully, but these errors were encountered: