http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55431
Alan Modra changed:
What|Removed |Added
Target Milestone|--- |4.8.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55431
Alan Modra changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
URL|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55431
--- Comment #9 from Alan Modra 2013-02-15 13:53:47
UTC ---
Author: amodra
Date: Fri Feb 15 13:53:40 2013
New Revision: 196077
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=196077
Log:
PR target/55431
* config/rs6000/l
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55431
--- Comment #8 from Rich Felker 2013-02-12 15:27:58
UTC ---
Is there nothing internal in the sigcontext structure that distinguishes the
version?
Making the reference to __libc_stack_end weak won't help. If the symbol is
undefined, the
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55431
--- Comment #7 from Alan Modra 2013-02-12 13:23:59
UTC ---
On thinking about this a little more, the idea of using /proc/self/auxv isn't
that good. MD_FALLBACK_FRAME_STATE_FOR is only needed for older kernels;
Kernels 2.6.15 and later pr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55431
--- Comment #6 from Rich Felker 2013-02-12 07:08:14
UTC ---
That sounds highly doubtful. The sigcontext is (necessarily) on the stack, so
the only way accessing past the end of sigcontext could fault is if the access
were so far beyond the
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55431
--- Comment #5 from Alan Modra 2013-02-12 03:04:28
UTC ---
Created attachment 29420
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29420
use /proc/self/auxv
At the time the original code was being developed, linux-2.4.x was in
wid
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55431
Alan Modra changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|amodra
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55431
David Edelsohn changed:
What|Removed |Added
Target||powerpc*-*-linux
St
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55431
Bernhard Reutner-Fischer changed:
What|Removed |Added
CC||aldot at gcc dot gnu.or
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55431
--- Comment #2 from Rich Felker 2012-12-09 02:37:19
UTC ---
The ABI issue is a dependency on an undocumented part of glibc's ABI behavior
-- I don't see anywhere it's documented that __libc_stack_end points at "argc"
(i.e. the original pla
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55431
--- Comment #1 from Andrew Pinski 2012-12-09
00:59:40 UTC ---
There seems like there are two different issues here. The first issue if musl
libc not following the same ABI as glibc. The second issues looks like maybe a
real one.
12 matches
Mail list logo
