patches/glibc/ports-2.13/330-m68k-sys-user.patch
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Tue May 03 00:19:56 2011 +0200 (2011-05-03)
changeset 2438 2ba5655f6297
permissions -rw-r--r--
libc/glibc: add 2.13

Patchset provided by "Ioannis E. Venetis" <venetis@mail.capsl.udel.edu>
http://sourceware.org/ml/crossgcc/2011-04/msg00072.html
http://sourceware.org/ml/crossgcc/2011-04/msg00073.html

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
     1 copied from kernel as it is sanitized now
     2 
     3 diff -durN glibc-2.13.orig/glibc-ports-2.13/sysdeps/unix/sysv/linux/m68k/sys/user.h glibc-2.13/glibc-ports-2.13/sysdeps/unix/sysv/linux/m68k/sys/user.h
     4 --- glibc-2.13.orig/glibc-ports-2.13/sysdeps/unix/sysv/linux/m68k/sys/user.h	2009-05-16 10:36:20.000000000 +0200
     5 +++ glibc-2.13/glibc-ports-2.13/sysdeps/unix/sysv/linux/m68k/sys/user.h	2009-11-13 00:50:31.000000000 +0100
     6 @@ -1,3 +1,90 @@
     7 +#ifndef _SYS_USER_H
     8 +#define _SYS_USER_H
     9 +
    10 +/* Core file format: The core file is written in such a way that gdb
    11 +   can understand it and provide useful information to the user (under
    12 +   linux we use the 'trad-core' bfd).  There are quite a number of
    13 +   obstacles to being able to view the contents of the floating point
    14 +   registers, and until these are solved you will not be able to view the
    15 +   contents of them.  Actually, you can read in the core file and look at
    16 +   the contents of the user struct to find out what the floating point
    17 +   registers contain.
    18 +   The actual file contents are as follows:
    19 +   UPAGE: 1 page consisting of a user struct that tells gdb what is present
    20 +   in the file.  Directly after this is a copy of the task_struct, which
    21 +   is currently not used by gdb, but it may come in useful at some point.
    22 +   All of the registers are stored as part of the upage.  The upage should
    23 +   always be only one page.
    24 +   DATA: The data area is stored.  We use current->end_text to
    25 +   current->brk to pick up all of the user variables, plus any memory
    26 +   that may have been malloced.  No attempt is made to determine if a page
    27 +   is demand-zero or if a page is totally unused, we just cover the entire
    28 +   range.  All of the addresses are rounded in such a way that an integral
    29 +   number of pages is written.
    30 +   STACK: We need the stack information in order to get a meaningful
    31 +   backtrace.  We need to write the data from (esp) to
    32 +   current->start_stack, so we round each of these off in order to be able
    33 +   to write an integer number of pages.
    34 +   The minimum core file size is 3 pages, or 12288 bytes.
    35 +*/
    36 +
    37 +struct user_m68kfp_struct {
    38 +	unsigned long  fpregs[8*3];	/* fp0-fp7 registers */
    39 +	unsigned long  fpcntl[3];	/* fp control regs */
    40 +};
    41 +
    42 +/* This is the old layout of "struct pt_regs" as of Linux 1.x, and
    43 +   is still the layout used by user (the new pt_regs doesn't have
    44 +   all registers). */
    45 +struct user_regs_struct {
    46 +	long d1,d2,d3,d4,d5,d6,d7;
    47 +	long a0,a1,a2,a3,a4,a5,a6;
    48 +	long d0;
    49 +	long usp;
    50 +	long orig_d0;
    51 +	short stkadj;
    52 +	short sr;
    53 +	long pc;
    54 +	short fmtvec;
    55 +	short __fill;
    56 +};
    57 +
    58 +
    59 +/* When the kernel dumps core, it starts by dumping the user struct -
    60 +   this will be used by gdb to figure out where the data and stack segments
    61 +   are within the file, and what virtual addresses to use. */
    62 +struct user{
    63 +/* We start with the registers, to mimic the way that "memory" is returned
    64 +   from the ptrace(3,...) function.  */
    65 +  struct user_regs_struct regs;	/* Where the registers are actually stored */
    66 +/* ptrace does not yet supply these.  Someday.... */
    67 +  int u_fpvalid;		/* True if math co-processor being used. */
    68 +                                /* for this mess. Not yet used. */
    69 +  struct user_m68kfp_struct m68kfp; /* Math Co-processor registers. */
    70 +/* The rest of this junk is to help gdb figure out what goes where */
    71 +  unsigned long int u_tsize;	/* Text segment size (pages). */
    72 +  unsigned long int u_dsize;	/* Data segment size (pages). */
    73 +  unsigned long int u_ssize;	/* Stack segment size (pages). */
    74 +  unsigned long start_code;     /* Starting virtual address of text. */
    75 +  unsigned long start_stack;	/* Starting virtual address of stack area.
    76 +				   This is actually the bottom of the stack,
    77 +				   the top of the stack is always found in the
    78 +				   esp register.  */
    79 +  long int signal;		/* Signal that caused the core dump. */
    80 +  int reserved;			/* No longer used */
    81 +  struct user_regs_struct *u_ar0;
    82 +				/* Used by gdb to help find the values for */
    83 +				/* the registers. */
    84 +  struct user_m68kfp_struct* u_fpstate;	/* Math Co-processor pointer. */
    85 +  unsigned long magic;		/* To uniquely identify a core file */
    86 +  char u_comm[32];		/* User command that was responsible */
    87 +};
    88 +#define NBPG 4096
    89 +#define UPAGES 1
    90 +#define HOST_TEXT_START_ADDR (u.start_code)
    91 +#define HOST_STACK_END_ADDR (u.start_stack + u.u_ssize * NBPG)
    92 +
    93 +#endif
    94  /* Copyright (C) 2008, 2010 Free Software Foundation, Inc.
    95     This file is part of the GNU C Library.
    96  
    97 diff -durN glibc-2.13.orig/ports/sysdeps/unix/sysv/linux/m68k/sys/user.h glibc-2.13/ports/sysdeps/unix/sysv/linux/m68k/sys/user.h