Re: [PR 78140] Reuse same IPA bits and VR info

2017-02-28 Thread jh
According to my measurements, the patch saves about 1.2 GB of memory. The problem is that some change last week (between revision 245382 and 245595) has more than invalidated this: | compiler| WPA mem (GB) | |-+--| | gcc 6 branch|

Re: [RFC PATCH 3/3] Remove ipa_update_after_lto_read

2017-02-28 Thread jh
Dne 2017-02-27 17:35, Martin Jambor napsal: Hello, when working on call summaries, I have found a weird function ipa_update_after_lto_read which currently only makes sure that IPA-CP function and edge summaries exist, at times when they already have to exist. So I did some digging in history

Re: [RFC PATCH 1/3] call_summary to keep info about cgraph_edges

2017-02-28 Thread jh
Dne 2017-02-27 17:35, Martin Jambor napsal: Hello, this patch is an actual implementation of the call_summary class (I hope the name is a good analogy to the function_summary we have, I am opened to other suggestions). I have kept the implementation close to the existing one of

Re: [RFC PATCH 2/3] Use call_summary in ipa-prop and ipa-cp

2017-02-28 Thread jh
Dne 2017-02-27 17:35, Martin Jambor napsal: Hello, this is patch is afairly straightforward conversion from use of a vector indexed by edge->uid to use of the new call_summary from the previous patch. The patch is generally a cleanup, hashing is a nicer method of keeping call-site related

Re: [PATCH 0/4] Properly handle GCC target("march=") (PR71652)

2016-09-22 Thread jh
OK for patches 1-4. Honza Dne 2016-08-12 14:15, Martin Liška napsal: PING^1 Hello. Following small patch set targets $subject, where we ICE if someone uses #pragma GCC target ("arch=generic"). My attempt is to not to create a new target optimization node in case of a wrong value of march