search for: getelem

I need help with creating custom xml reader for use with the tm package. The objective is to crate a corpus for analysis. Files that I'm working with come from solr and are in a funky XML format never the less I'm able to parse the XML files using solrDocs.R function provided by Duncan Temple Lang. The problem I'm having that once I parse the document I need to create a custom

...t;> this information: It removes any bitcasts from a subset to a superset >> address space. It gets at the address space information by requiring the >> TargetAddrspaces analysis, which will give it the default implementation in >> all current tools. > > For the case of a GetElementPointer, we are replacing a bitcast to a > pointer, getelem with a getelem bitcast. The assumption is the latter > bitcast will hopefully go away when we iterate through those uses. Uh? Is this a comment about what the current code or my patch does, or what it should do? I don't unde...

...; use of this > information: It removes any bitcasts from a subset to a superset > address > space. It gets at the address space information by requiring the > TargetAddrspaces analysis, which will give it the default > implementation in > all current tools. For the case of a GetElementPointer, we are replacing a bitcast to a pointer, getelem with a getelem bitcast. The assumption is the latter bitcast will hopefully go away when we iterate through those uses. > > > So, this requires a minimal amount of changes, the current code > won't know the > dif...

...ver create a concrete class from TargetAddrSpace that doesn't also derive > from ImmutablePass? If not, I don't think is worth using multiple > inheritance in this case. I think you are right here, changing the inheritance in this way also works fine. >>> For the case of a GetElementPointer, we are replacing a bitcast to a >>> pointer, getelem with a getelem bitcast. The assumption is the latter >>> bitcast will hopefully go away when we iterate through those uses. >> Uh? Is this a comment about what the current code or my patch does, or what >&gt...

...a >>> superset >>> address space. It gets at the address space information by >>> requiring the >>> TargetAddrspaces analysis, which will give it the default >>> implementation in >>> all current tools. >> >> For the case of a GetElementPointer, we are replacing a bitcast to a >> pointer, getelem with a getelem bitcast. The assumption is the >> latter >> bitcast will hopefully go away when we iterate through those uses. > Uh? Is this a comment about what the current code or my patch does, > or what i...

Hi Mon Ping, I've again attached a patch, wich lets LLVM know about about the relations between different address spaces. Instead of cramming this info in with TargetData (with all kinds of unwanted side effects, especially for the IR), I opted to create a new pass, TargetAddrspaces, which holds this information. Just like TargetData, this can be added to the passmanager by the tool running