<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 4, 2016 at 6:50 PM, Todd Fiala via swift-lldb-dev <span dir="ltr"><<a href="mailto:swift-lldb-dev@swift.org" target="_blank">swift-lldb-dev@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><span class=""><blockquote type="cite"><div>On Dec 28, 2015, at 10:39 AM, William Dillon via swift-lldb-dev <<a href="mailto:swift-lldb-dev@swift.org" target="_blank">swift-lldb-dev@swift.org</a>> wrote:</div><br><div><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">Hi Todd,</span><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br></div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">Yes, I think that LLDB is more or less working with Swift on ARM. We can start the REPL and do some tasks with it, though it isn’t all that reliable yet.</div></div></blockquote><div><br></div></span><div>I’d love to hear about the reliability piece if you have more details there!</div><span class=""><br><blockquote type="cite"><div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"> There are two files in the swift-lldb PR that I merged in from Joe Bell that fixed the REPL. I think, however, than they would need to go to the<span> </span><a href="http://lldb.llvm.org/" target="_blank">lldb.llvm.org</a> repo, rather than the swift one.</div></div></blockquote><div><br></div></span><div>I think I’ve seen the <a href="http://llvm.org" target="_blank">llvm.org</a> side of that patch. Somebody else and I had a question about some static casts in there, but we’ll catch up on that side if it is the same patch I’m thinking about.</div><span class=""><br><blockquote type="cite"><div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"> There is a question about that, though. Joe added armv7l into the ArchSpec table, but I don’t think that armv7l is a real subtype. I’ve been very confused by the ARM nomenclature on linux (I don’t think I’m alone here), and I think that armv7l means armv7 little endian. So, should these get converted to armv7 somewhere else and revert the changes to the ArchSpec table?</div></div></blockquote><div><br></div></span><div>This is a great question that I am not the right resource to answer. <b>Greg or Jason,</b> any thoughts here on question of arm subtypes? (My first take is that I’d expect each subtype to represent a different set of features and instructions available, and not be used solely for an endianness designation, but that’s not an area I do much work in).</div></div></div></blockquote><div> </div><div>We have discussed this before with Tim Northover, and he suggested that we canonicalize armv7l to armv7 when parsing the triple from the command line.</div><div><br></div><div>Dmitri</div></div><div><br></div>-- <br><div class="gmail_signature">main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if<br>(j){printf("%d\n",i);}}} /*Dmitri Gribenko <<a href="mailto:gribozavr@gmail.com" target="_blank">gribozavr@gmail.com</a>>*/</div>
</div></div>