|
Message-ID: <CACsECNc+Vu2LSPY1zaua9Cn9v61sLweMDU+Sfcnou8OvmDwNKQ@mail.gmail.com> Date: Wed, 8 Jul 2015 16:24:45 +0200 From: Alex <alexinbeijing@...il.com> To: musl@...ts.openwall.com Subject: Re: [PATCH v9] Build process uses script to add CFI directives to x86 asm >> Then there are some labels which are declared as ".global" and >> ".hidden", like __memcpy_fwd, __exp2l, and ___setjmp. It looks like >> when any of those 3 are reached, there should be a return address on >> top of the stack. What would you think of adding a ".type @function" >> declaration for those 3, so that the CFI generation script will treat >> them as "functions"? > > Do these matter? The exact same address is already an entry point > via the other public name(s) you're supposed to use for it. You're right, I just looked at the source and they don't matter.
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.