search for: 289661

...there is > > no > > > single correct source location for the new instruction, and > > typically > > > erasing the source location will give a better debugging experience > > (also > > > a less misleading profile). > > For the record: revision 289661 ( > http://llvm.org/viewvc/llvm-project?view=revision&revision=289661 ) > added a new API to obtain a merged/combined location from multiple > source locations. That said, the new functionality added at that > revision is just a stub. So, it is still unclear at the moment how > w...

...t > source locations, that's a separate problem. In that case there is no > single correct source location for the new instruction, and typically > erasing the source location will give a better debugging experience (also > a less misleading profile). > For the record: revision 289661 (http://llvm.org/viewvc/llvm- project?view=revision&revision=289661) added a new API to obtain a merged/combined location from multiple source locations. That said, the new functionality added at that revision is just a stub. So, it is still unclear at the moment how we could 'use' that...

>> I don't know what the right, if any, solution to this is - but I >> thought I should bring it up in case you or anyone else wanted to >> puzzle it over & see if the competing needs/desires might need to be >> considered. > One thing that I recall being discussed was changing the way that we > set the is_stmt flag in the DWARF line-table information. As I

I want to get some "simple" logic regression examples to work before exploring a hard problem. I can get results, but I'm having some problems using "cat" to save the logic regression equation to a disk file. Consider this: # Simple Logic Regression Example # efg, 23 Feb 2005 library(LogicReg) # Create simulated data with known logic equation: # "noise"