similar to: [LLVMdev] ARM unwinding bug

On 29 July 2015 at 16:53, Mason Wheeler <masonwheeler at yahoo.com> wrote: > A couple weeks ago, Ben Pye, a developer working on the ARM32 stuff, found > and reported a bug related to incorrect generation of stack unwinding info. > ( https://llvm.org/bugs/show_bug.cgi?id=24146 ) Apparently it only occurs > under a highly specific set of circumstances, which might look like a

> From: Renato Golin <renato.golin at linaro.org> > > > On 29 July 2015 at 16:53, Mason Wheeler <masonwheeler at yahoo.com> wrote: > > A couple weeks ago, Ben Pye, a developer working on the ARM32 stuff, found > > and reported a bug related to incorrect generation of stack unwinding info. > > ( https://llvm.org/bugs/show_bug.cgi?id=24146 ) Apparently it

> From: Renato Golin <renato.golin at linaro.org> > > On 29 July 2015 at 20:14, Mason Wheeler <masonwheeler at yahoo.com> wrote: > > Well, yes, an unwinding expert *was* who I was really hoping to hear from. But > > if I understand correctly, you're saying that rather than seeing the values Ben > > reported, the sample code crashes on you on both

On 29 July 2015 at 20:14, Mason Wheeler <masonwheeler at yahoo.com> wrote: > Well, yes, an unwinding expert *was* who I was really hoping to hear from. But > if I understand correctly, you're saying that rather than seeing the values Ben > reported, the sample code crashes on you on both compilers? I do notice that > you're using different versions of both compilers

On 29 July 2015 at 22:23, Mason Wheeler <masonwheeler at yahoo.com> wrote: > That would be Ben. :) We'll get there, eventually... :) > Meh. It's more of a "if you build it, they will come" thing. We haven't > finished building it yet, but when we do, they *will* come! :D Thought so. Ben will have to learn a lot about unwinding, then... :D > Genuine

Hi Ben, I am aware of the bug. I have downloaded the test case and look around few days ago. However, I am still trying to figure out the situation. Thus, I have no further comments at the moment. BTW, as an amateur LLVM developer, I am fixing the issues with my spare time, thus I have to prioritize the tasks (3.7 release gets much higher priority currently) and sorry for not being

> There are a lot of Windows folks in LLVM, and certainly good support > for it, including on ARM, so maybe that would get more traction and > even get done quicker than trying to debug here a problem in an > external library. Even though you want your CoreCLR to work on > Android, I assume this will be mainly developed from a Windows IDE, so > IDE folks that know a thing or two

On 29 July 2015 at 23:11, Ben Pye <ben at curlybracket.co.uk> wrote: > 4.8.4, again packaged from Ubuntu 14.04 LTS, not sure if they include any > patches that'd change this behaviour. This should be similar to 4.8.2 that I have, so no worries there. cheers, --renato

> You should also realise that using another libunwind makes matters > more complex, because now it's far less likely that the LLVM's > libunwind folks will be interested in fixing that... I certainly understand the issue in using PathScale's libunwind, but the lack of unw_get_save_loc is somewhat problematic and means that it is preferable to use the other libunwind within

> Yes, so, that's yet another missing info. Which ARM? RaspberyPi, > although popular, is a very old and somewhat deprecated architecture > (ARMv6). Most people work on ARMv7 and ARMv8 nowadays, so if you can't > reproduce the bugs on those, you'll have a hard time finding people to > help you. > Also, Clang 3.6 is not that old, but we don't really provide >

On 29 July 2015 at 22:46, Ben Pye <ben at curlybracket.co.uk> wrote: > I certainly understand the issue in using PathScale's libunwind, but the > lack of unw_get_save_loc is somewhat problematic and means that it is > preferable to use the other libunwind within coreclr. Or, you could try to persuade people to implement that in LLVM? There are a lot of Windows folks in LLVM,

On Sun, Jun 24, 2012 at 1:11 PM, Mason Wheeler <masonwheeler at yahoo.com> wrote: > Hi all, > > I'm trying to build LLVM, synced from SVN trunk yesterday. > > I ran CMake and it generated VS 2008 project files, so far so good.  Then I > tried to build them, by building the ALL_BUILD project. > > It got the first three all right, but choked on template issues in

On 20 March 2014 02:09, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > I think this is just 2. It uses .eh_frame for unwinding proper. The > only difference in .eh_frame is that there is a personality function > defined. If there is no debug information, it should still be possible to unwind the stack via the saved LR on the stack, no? If there is only line info, you

Folks, I'm sorry for getting at this again, but this will not be the last discussion on the topic, so let's just get to business. We're about to merge the last critical patch to make EHABI compatible with other EH mechanisms in LLVM (D3079), and that has unearthed a few issues with the function attributes. Logan's blog post [1] contains a proposal to split unwinding from

On 21 March 2014 18:47, Logan Chien <tzuhsiang.chien at gmail.com> wrote: > * There's the table for ARM target: > > - no attribute => emit unwind table > - with nounwind => emit unwind table with cantunwind > - with uwtable => emit unwind table > - with uwtable+nounwind => emit unwind table WITHOUT the cantunwind > > The cantunwind record will stop the

On 29 July 2015 at 22:20, Ben Pye <ben at curlybracket.co.uk> wrote: > Not sure if you got the other message, I think I managed to split the topic > as I wasn't subscribed to receive the previous message. This error has been > on the Raspberry Pi 2, so that's a Cortex A7 I believe, certainly ARMv7. Excellent! > I > haven't yet built trunk as on the device I run

On Thu, Feb 13, 2014 at 5:52 PM, Renato Golin <renato.golin at linaro.org> wrote: > On 13 February 2014 13:47, Evgeniy Stepanov <eugenis at google.com> wrote: >> Hm, I see that -funwind-tables on arm-linux-androideabi target >> replaces this "cantunwind" with a proper unwind table. >> Hence http://llvm-reviews.chandlerc.com/D2762. > > If Android is

Hi all, I'm trying to build LLVM, synced from SVN trunk yesterday. I ran CMake and it generated VS 2008 project files, so far so good.  Then I tried to build them, by building the ALL_BUILD project. It got the first three all right, but choked on template issues in LLVMCore: 1>------ Build started: Project: LLVMCore, Configuration: Debug Win32 ------ 1>Compiling... 1>Verifier.cpp

Hi all, I have a qemu-system-arm machine that I am currently starting using: qemu-system-arm -M versatilepb -nographic \ -hda img.qcow2 \ -net vde,vlan=0,sock=/var/run/qemu-vde.ctl \ -net nic,vlan=0,macaddr=52:54:00:12:34:22 \ -kernel vmlinuz-2.6.18-6-versatile \ -initrd initrd.img-2.6.18-6-versatile \ -append "root=/dev/sda1

Dear LLVM people, I have started playing with LLVM a little bit and I am thinking of using it to write some linear algebra software for my class. First, an off-topic "bug report" (?), I tried using llvm under cygwin with Vista 64 bits, and it hangs during the build process. It works fine under Vista 32 bits, with cygwin. I was reading the documentation and I am very excited by the