From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Modules and CONFIG_ALTIVEC
Date: Sun, 5 Aug 2001 23:38:29 -0700 [thread overview]
Message-ID: <20010805233829.A27436@nevyn.them.org> (raw)
In-Reply-To: <01080518082100.00490@silence.internal>; from hollis-lists@austin.rr.com on Sun, Aug 05, 2001 at 06:08:21PM -0500
On Sun, Aug 05, 2001 at 06:08:21PM -0500, Hollis wrote:
>
> On Sunday 05 August 2001 04:49, Samuel Rydh wrote:
> > On ppc, the size of thread_struct depends on the CONFIG_ALTIVEC setting.
> > Thus, the offset of various task_struct fields are dependent upon this
> > config option.
> [snip]
> > unsigned long fpscr; /* Floating point status */
> > -#ifdef CONFIG_ALTIVEC
> > - vector128 vr[32]; /* Complete AltiVec set */
> > - vector128 vscr; /* AltiVec status */
> > - unsigned long vrsave;
> > -#endif /* CONFIG_ALTIVEC */
> > + altivec_t *vregs;
>
> This also affects gdb. When gdb reads a core file, it gets upset if the size
> of a regset isn't what it thinks it should be. Currently it's a bit too easy
> to change that size...
Yup. Expect GDB patches to deal with that (and with altivec) from me
in the next month, if no one beats me to it. It's approaching the top
of my TODO list.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-08-06 6:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-05 21:49 Modules and CONFIG_ALTIVEC Samuel Rydh
2001-08-05 23:08 ` Hollis
2001-08-06 6:38 ` Daniel Jacobowitz [this message]
2001-08-06 8:09 ` Franz Sirl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010805233829.A27436@nevyn.them.org \
--to=dmj+@andrew.cmu.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).