search for: snode

Hi, I often find myself staring at IR and wanting to look at the C source code it corresponds to. To do so, I look up the debug identifier for the given IR line, scroll to the bottom of the IR file to find the debug identifier, look at the debug location (source and column), and then look at the source file. Too many steps. What would be great is a tool that took two files, i.e., a .c file and a

...tions in the function will need to > use them (though different metadata arguments may be used in different > scopes). So I think that opens our options a bit. If the pragma applies to the entire function then would it be as simple as a pass to convert intrinsic calls into whatstheterm SNodes (?) after the optimization passes have run? Meaning, we can bypass any changes to the AST? That would still leave the backend changes to be done, of course. BTW, I thought that optimization passes were allowed to drop metadata. So what happens to the metadata on the constrained intrinsic calls?...

...rs(list)) + + def format_memchunks(self, pinfo): + str='''' + whitespace='''' + try: + chunk=pinfo[''mem_chunks''] + for i in range(0, pinfo[''nr_nodes'']): + str+=''%snode%d:0x%016x-0x%016x\n'' % (whitespace, + chunk[i][''node''], + chunk[i][''start_paddr''], + chunk[i]['&...

...28"=>""} Show session dump --- iNode: "" frm_txtName: frm_txtUrl: frm_txtDynamicObjectParameters: frm_cboIcon: :flashdiv_count: 7268 trusted: ad frm_cat32: :node_restrict: 0 frm_exhibit_id: "0" frm_action: portalContent_01 frm_cat33: :portal_name: hoist_sv_SE2 sNode: "" frm_txtIspBandw: frm_chkActive: "on" frm_cat34: frm_chkIspReq: frm_cat35: sTVPortal: hoist_sv_SE2 uid: html err: Err: "" exhibit_id: frm_cboDynamicObject: :contentportal: hoist_sv_SE2 frm_cat36: :sOperator: "3" :include_count: 67811 pg-databases: frm_txtS...

Andrew Kaylor wrote: >In general, the current "strict FP" handling stops at instruction >selection. At the MachineIR level we don't currently have a mechanism >to prevent inappropriate optimizations based on floating point >constraints, or indeed to convey such constraints to the backend. >Implicit register use modeling may provide some restriction on some

(Second try to send this. I wonder if the first one gotten eaten by a spam filter; I'll link to patches instead of attaching them.) Here are the tincctl patches I've been working on. They apply to http://www.tinc-vpn.org/svn/tinc/branches/1.1@1545. I intend to commit them once the crypto stuff's fixed. Since they're basically done, I'm emailing them now for review and in case