[lldb-dev] Discrete code and data memories

I'm trying to implement LLDB support for an architecture where code and data stores can be explicitly separated and can even have overlapping addresses (one can think of it as ROM and RAM, with separate access buses). My impression is that LLDB somewhat presumes a hybrid memory map, e.g. the clien

Re: [lldb-dev] netbsd7 buildbot broken

I modified those scripts recently (it's these scripts , for those who don't know what we are talking about), and I accidentally broke that. I am sorry about that, it should be fix

Re: [lldb-dev] Discrete code and data memories

I believe that some of the DSPs we have support for (Hexagon?) has this kind of issue. I would speak to Ted Woodward and see if they do anything special for this. Greg Clayton > On May 25, 2016, at 2:16 AM, Tyro Software via lldb-dev > wrote: > > I'm trying to implement LLDB support for an a

[lldb-dev] [Bug 27883] New: TestConstVariables.py fails on arm/aarch64 linux targets failing frame variable type lookup

https://llvm.org/bugs/show_bug.cgi?id=27883 Bug ID: 27883 Summary: TestConstVariables.py fails on arm/aarch64 linux targets failing frame variable type lookup Product: lldb Version: unspecified Hardware: PC

Re: [lldb-dev] [Attn: Bot Owners!] Raising CMake minimum version to 3.4.3

I am ready, regarding to, http://bb.pgr.jp/ On Wed, May 25, 2016 at 5:54 AM Chris Bieneman wrote: > Meant to send this yesterday, but I want to remind everyone that we’re > going to be raising the CMake minimum version to 3.4.3 next week. > > If you maintain bots please ensure that your bots are

Re: [lldb-dev] netbsd7 buildbot broken

It's now clear. Thank you! On 25.05.2016 11:30, Pavel Labath wrote: > I modified those scripts recently (it's these scripts > , > for those who don't know what we are talking abo

Re: [lldb-dev] Discrete code and data memories

What Tyro is describing is called a "Harvard architecture" - https://en.wikipedia.org/wiki/Harvard_architecture . It contrasts with the von Neumann architecture used by most machines today. Hexagon has a unified memory map, but I've worked with other DSPs (Motorola DSP56xxx) that have a code bu