David O'Brien wrote:
> > Ports does the same thing: hand tweaks stuff instead of
> > pushing the patches back to the projects that originated
> > it.
>
> *sigh* Terry I respect your programming knowledge, but you are wrong
> here. I send out a *LOT* of patches to the authors of ports I maintain
--=-c5mu7fd8+iIeadXPJgcR
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
On Thu, 2002-02-07 at 08:01, Julian Elischer wrote:
>=20
> for the set of patches at:
> http://www.freebsd.org/~julian/adiff
>=20
> these patches SHOULD NOT EFFECT your system except to do some
> slight
I don't know the alpha at all but
how about
leaq t0, thread0
or some similar thing
or even..
ldq t0,$thread0
or something similar..
who's assembler is being used?
On Wed, 6 Feb 2002, Andrew Gallatin wrote:
>
> Andrew Gallatin writes:
> >
> > Since thread0 is no longer a pointer, t
Julian Elischer writes:
>
> for the set of patches at:
> http://www.freebsd.org/~julian/adiff
>
> these patches SHOULD NOT EFFECT your system except to do some
> slight re-aranging of stuff in the kernel.
Today's alpha kernel, plus those changes results in a ksp not valid
halt with the P
Apparently, On Wed, Feb 06, 2002 at 12:01:44PM -0800,
Julian Elischer said words to the effect of;
>
> for the set of patches at:
> http://www.freebsd.org/~julian/adiff
>
> these patches SHOULD NOT EFFECT your system except to do some
> slight re-aranging of stuff in the kernel.
>
> TH
Apparently, On Wed, Feb 06, 2002 at 06:17:38PM -0500,
Andrew Gallatin said words to the effect of;
>
> Andrew Gallatin writes:
> >
> > Since thread0 is no longer a pointer, this looks suspicious in locore.s:
> >
> > /*
> > * Switch to proc0's PCB.
> > */
Ok so since I don't know alpha assembly.
can it be changed to teh address of the thread0 structure?
(I'll bet the same thing needs to be done on the other
architectures)
THANKS!
On Wed, 6 Feb 2002, Andrew Gallatin wrote:
>
> Julian Elischer writes:
> >
> > for the set of patches at:
> >
On Wed, Feb 06, 2002 at 12:32:18PM -0800, Alfred Perlstein wrote:
> * Julian Elischer <[EMAIL PROTECTED]> [020206 12:20] wrote:
> >
> > for the set of patches at:
> > http://www.freebsd.org/~julian/adiff
> >
> > these patches SHOULD NOT EFFECT your system except to do some
> > slight re-aranging
for the set of patches at:
http://www.freebsd.org/~julian/adiff
these patches SHOULD NOT EFFECT your system except to do some
slight re-aranging of stuff in the kernel.
THe aim is to get this committed to 'clarify' the upcoming
KSE commit in http://www.freebsd.org/~julian/thediff
which include
Julian Elischer writes:
>
>
> I've committed both the kernel diff and a libkvm diff that seems to work
> for me here.
>
> can you check it with the new -current again ?
World breakage on alpha:
usr/src/gnu/usr.bin/binutils/gdb/alpha/kvm-fbsd.c: In function `set_proc_cmd':
/usr/src/gnu
On Wed, Feb 06, 2002 at 06:54:22PM -0800, Terry Lambert wrote:
> Julian Elischer wrote:
> > how about a port that uses the installed sources
> > together with some uploaded parts to 'reconstitute' gcj as if it had been
> > compiled wit the rest of the system.
>
> FreeBSD does a fairly evil thing:
I've committed both the kernel diff and a libkvm diff that seems to work
for me here.
can you check it with the new -current again ?
On Wed, 6 Feb 2002, Andrew Gallatin wrote:
>
> Jake Burkholder writes:
> > > What's the "right" way to do this?
> >
> > I think you want lda, its used t
* Julian Elischer <[EMAIL PROTECTED]> [020206 12:20] wrote:
>
> for the set of patches at:
> http://www.freebsd.org/~julian/adiff
>
> these patches SHOULD NOT EFFECT your system except to do some
> slight re-aranging of stuff in the kernel.
>
> THe aim is to get this committed to 'clarify' the
ok here's the fix that went into libkvm
http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libkvm/kvm_proc.c.diff?r1=1.41&r2=1.42
basically you have to map in the thread structure separatly to the
proc structure, using the first entry in the linked list of threads.
Obviously this only works for a pr
Julian Elischer writes:
>
>
> I've committed both the kernel diff and a libkvm diff that seems to work
> for me here.
>
> can you check it with the new -current again ?
World breakage on alpha:
usr/src/gnu/usr.bin/binutils/gdb/alpha/kvm-fbsd.c: In function `set_proc_cmd':
/usr/src/gnu
On Thu, Feb 07, 2002 at 04:28:03PM -0500, Andrew Gallatin wrote:
>
> Julian Elischer writes:
> >
> >
> > I've committed both the kernel diff and a libkvm diff that seems to work
> > for me here.
> >
> > can you check it with the new -current again ?
> >
>
> I'll build a kernel & I'll
David O'Brien wrote:
> > Ports does the same thing: hand tweaks stuff instead of
> > pushing the patches back to the projects that originated
> > it.
>
> *sigh* Terry I respect your programming knowledge, but you are wrong
> here. I send out a *LOT* of patches to the authors of ports I maintain
Julian Elischer writes:
>
>
> I've committed both the kernel diff and a libkvm diff that seems to work
> for me here.
>
> can you check it with the new -current again ?
>
I'll build a kernel & I'll be happy to try a buildworld under it.
But from what I understand, the new binutils is
I've committed both the kernel diff and a libkvm diff that seems to work
for me here.
can you check it with the new -current again ?
On Wed, 6 Feb 2002, Andrew Gallatin wrote:
>
> Jake Burkholder writes:
> > > What's the "right" way to do this?
> >
> > I think you want lda, its used t
thread0 is not the structure itself rather than a pointer
that should be the only difference that should affect MD code
On 7 Feb 2002, Benno Rice wrote:
> On Thu, 2002-02-07 at 08:01, Julian Elischer wrote:
> >
> > for the set of patches at:
> > http://www.freebsd.org/~julian/adiff
> >
> > th
On Thu, Feb 07, 2002 at 12:41:33AM -0800, Terry Lambert wrote:
>
> Ports does the same thing: hand tweaks stuff instead of
> pushing the patches back to the projects that originated
> it.
*sigh* Terry I respect your programming knowledge, but you are wrong
here. I send out a *LOT* of patches to
On Thu, 2002-02-07 at 08:01, Julian Elischer wrote:
>
> for the set of patches at:
> http://www.freebsd.org/~julian/adiff
>
> these patches SHOULD NOT EFFECT your system except to do some
> slight re-aranging of stuff in the kernel.
>
> THe aim is to get this committed to 'clarify' the upcoming
Peter Wemm wrote:
> The following files:
> src/gnu/usr.bin/cc/cc_tools/auto-host.h
> src/gnu/usr.bin/cc/cc_tools/freebsd-native.h
> .. are vaguely based on stuff that configure generated and are hand tweaked
> to deal with the *freebsd* environment (eg: whether printf supports %p
> etc), rathe
On 06-Feb-02 Andrew Gallatin wrote:
>
> Andrew Gallatin writes:
> >
> > Since thread0 is no longer a pointer, this looks suspicious in locore.s:
> >
> > /*
> > * Switch to proc0's PCB.
> > */
> > ldq t0,thread0 /* get phys addr of pcb *
Julian Elischer wrote:
>
>
> On Wed, 6 Feb 2002, Andrew Gallatin wrote:
>
> >
> > Jake Burkholder writes:
> > > > What's the "right" way to do this?
> > >
> > > I think you want lda, its used to load an address constant in support.s:
> > >
> > > lda t0, fusufault /
Terry Lambert wrote:
> Julian Elischer wrote:
> > how about a port that uses the installed sources
> > together with some uploaded parts to 'reconstitute' gcj as if it had been
> > compiled wit the rest of the system.
>
> FreeBSD does a fairly evil thing: it takes the compiler
> source code post-
On Wed, Feb 06, 2002 at 06:54:22PM -0800, Terry Lambert wrote:
> Julian Elischer wrote:
> > how about a port that uses the installed sources
> > together with some uploaded parts to 'reconstitute' gcj as if it had been
> > compiled wit the rest of the system.
>
> FreeBSD does a fairly evil thing:
Julian Elischer wrote:
> how about a port that uses the installed sources
> together with some uploaded parts to 'reconstitute' gcj as if it had been
> compiled wit the rest of the system.
FreeBSD does a fairly evil thing: it takes the compiler
source code post-config instead of pre-config.
It's
On Wed, 6 Feb 2002, Andrew Gallatin wrote:
>
> Jake Burkholder writes:
> > > What's the "right" way to do this?
> >
> > I think you want lda, its used to load an address constant in support.s:
> >
> > lda t0, fusufault /* trap faults */
>
> Bingo! Thanks.. I have
THANKS!
(3 down, 2 to go..)
On Wed, 6 Feb 2002, Jake Burkholder wrote:
> Apparently, On Wed, Feb 06, 2002 at 12:01:44PM -0800,
> Julian Elischer said words to the effect of;
>
> >
> > for the set of patches at:
> > http://www.freebsd.org/~julian/adiff
> >
> > these patches SHOULD NOT E
Apparently, On Wed, Feb 06, 2002 at 12:01:44PM -0800,
Julian Elischer said words to the effect of;
>
> for the set of patches at:
> http://www.freebsd.org/~julian/adiff
>
> these patches SHOULD NOT EFFECT your system except to do some
> slight re-aranging of stuff in the kernel.
>
> TH
On Wed, 6 Feb 2002, Andrew Gallatin wrote:
>
> Jake Burkholder writes:
> > > What's the "right" way to do this?
> >
> > I think you want lda, its used to load an address constant in support.s:
> >
> > lda t0, fusufault /* trap faults */
>
> Bingo! Thanks.. I have
Wilko Bulte <[EMAIL PROTECTED]> wrote:
> C'mon guys: it is not so long ago (days..) that the Alpha started
> buildworlding -current again.
I tried, and the new kernel blew up at start-up with an unaligned
access. GENERIC went farther, but died when /etc/rc redundandly
tried to load the osf1 mod
On Wed, Feb 06, 2002 at 08:15:29PM -0500, Jake Burkholder wrote:
> Apparently, On Wed, Feb 06, 2002 at 06:17:38PM -0500,
> Andrew Gallatin said words to the effect of;
>
> >
> > Andrew Gallatin writes:
> > >
> > > Since thread0 is no longer a pointer, this looks suspicious in locore.s:
Jake Burkholder writes:
> > What's the "right" way to do this?
>
> I think you want lda, its used to load an address constant in support.s:
>
> lda t0, fusufault /* trap faults */
Bingo! Thanks.. I haven't done any alpha assembler in nearly a year..
Julian -- you n
Ok so since I don't know alpha assembly.
can it be changed to teh address of the thread0 structure?
(I'll bet the same thing needs to be done on the other
architectures)
THANKS!
On Wed, 6 Feb 2002, Andrew Gallatin wrote:
>
> Julian Elischer writes:
> >
> > for the set of patches at:
> >
how about a port that uses the installed sources
together with some uploaded parts to 'reconstitute' gcj as if it had been
compiled wit the rest of the system.
On Wed, 6 Feb 2002, Mike Barcroft wrote:
> Wilko Bulte <[EMAIL PROTECTED]> writes:
> > C'mon guys: it is not so long ago (days..) that t
Apparently, On Wed, Feb 06, 2002 at 06:17:38PM -0500,
Andrew Gallatin said words to the effect of;
>
> Andrew Gallatin writes:
> >
> > Since thread0 is no longer a pointer, this looks suspicious in locore.s:
> >
> > /*
> > * Switch to proc0's PCB.
> > */
I don't know the alpha at all but
how about
leaq t0, thread0
or some similar thing
or even..
ldq t0,$thread0
or something similar..
who's assembler is being used?
On Wed, 6 Feb 2002, Andrew Gallatin wrote:
>
> Andrew Gallatin writes:
> >
> > Since thread0 is no longer a pointer, t
On Wed, Feb 06, 2002 at 06:20:16PM -0500, Mike Barcroft wrote:
> Wilko Bulte <[EMAIL PROTECTED]> writes:
> > C'mon guys: it is not so long ago (days..) that the Alpha started
> > buildworlding -current again. Alpha builds tend to take much
> > longer (on most people's hardware that is) so a bit of
Wilko Bulte <[EMAIL PROTECTED]> writes:
> C'mon guys: it is not so long ago (days..) that the Alpha started
> buildworlding -current again. Alpha builds tend to take much
> longer (on most people's hardware that is) so a bit of patience
> would be nice.
>
> FWIW: I'm trying to get 2 of my Alphas
Andrew Gallatin writes:
>
> Since thread0 is no longer a pointer, this looks suspicious in locore.s:
>
> /*
> * Switch to proc0's PCB.
> */
> ldq t0,thread0 /* get phys addr of pcb */
> ldq a0,TD_MD_PCBPADDR(t0)
> S
Julian Elischer writes:
>
> for the set of patches at:
> http://www.freebsd.org/~julian/adiff
>
> these patches SHOULD NOT EFFECT your system except to do some
> slight re-aranging of stuff in the kernel.
Today's alpha kernel, plus those changes results in a ksp not valid
halt with the P
On Wed, Feb 06, 2002 at 12:32:18PM -0800, Alfred Perlstein wrote:
> * Julian Elischer <[EMAIL PROTECTED]> [020206 12:20] wrote:
> >
> > for the set of patches at:
> > http://www.freebsd.org/~julian/adiff
> >
> > these patches SHOULD NOT EFFECT your system except to do some
> > slight re-aranging
* Julian Elischer <[EMAIL PROTECTED]> [020206 12:20] wrote:
>
> for the set of patches at:
> http://www.freebsd.org/~julian/adiff
>
> these patches SHOULD NOT EFFECT your system except to do some
> slight re-aranging of stuff in the kernel.
>
> THe aim is to get this committed to 'clarify' the
for the set of patches at:
http://www.freebsd.org/~julian/adiff
these patches SHOULD NOT EFFECT your system except to do some
slight re-aranging of stuff in the kernel.
THe aim is to get this committed to 'clarify' the upcoming
KSE commit in http://www.freebsd.org/~julian/thediff
which include
46 matches
Mail list logo
