------- Comment #9 from aldot at gcc dot gnu dot org 2010-03-08 19:28 ------- (In reply to comment #8) > What's the status of this bug ?
we currently still end up with call 0 on e.g. i386 > The same things can happen in libraries with fpic yes. Thing is that we could theoretically work around it by explicitly looking at the addr ¹) but that's just plain disgusting imho. And the hardened guys will not like the idea to drop DOPIC (i.e. build members of .a without PIC). So.. What's the status of that bug? Current binutils-2.20 and somewhat current gcc basically generate "wrong" code, or at least code that behaves in an unpleasant way causing grief.. ¹) https://bugs.uClibc.org/1033 thanks and cheers, -- aldot at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2010-03-08 19:28:29 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32219
