Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 01 Mar 2010 22:06:11 -0700 (MST)
From:      "M. Warner Losh" <imp@bsdimp.com>
To:        neelnatu@gmail.com
Cc:        freebsd-mips@freebsd.org
Subject:   Re: n32 support patches
Message-ID:  <20100301.220611.787670930824834909.imp@bsdimp.com>
In-Reply-To: <dffe84831003012043n119d5809s2e300e4b8bc35a35@mail.gmail.com>
References:  <98a59be81003010628g6099768erc397bc90841840f8@mail.gmail.com> <dffe84831003012043n119d5809s2e300e4b8bc35a35@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
In message: <dffe84831003012043n119d5809s2e300e4b8bc35a35@mail.gmail.co=
m>
            Neel Natu <neelnatu@gmail.com> writes:
: The changes to bsd.cpu.mk that append to LDFLAGS will most likely
: break building kernel modules. Can you build a kernel module in a tre=
e
: with your patch?

Chances are all of those will go away anyway :)  But I haven't thought
about ABI changes in my TBEMD tree....

: The problem is that LDFLAGS are directly passed as arguments to the
: linker in bsd.kmod.mk and the linker does not like the
: -Wl,-linker_option style of setting options.
: =

: Do you really need to set LDFLAGS in bsd.cpu.mk? It would seem that
: simply setting LD would work.

But in the current world order, I have the same questions...

Warner


: best
: Neel
: =

: On Mon, Mar 1, 2010 at 6:28 AM, C. Jayachandran
: <c.jayachandran@gmail.com> wrote:
: > I'm in the process of getting n32 ABI support for the RMI processor=
s.
: > The plan is have n32 compiled kernel with 64-bit register_t and
: > physaddr_t and 32 bit long and pointer types.
: >
: > I've attached two patches, one for support for n32 in toolchain and=

: > one for n32 support in kernel compilation. =A0With this I am able t=
o
: > compile the kernel and user space with n32, and the boot-up reaches=

: > until init. There is a lot more work on user-space and kernel (esp =
in
: > mips/mips/*.S) before it can complete boot-up.
: >
: > Please review and let me know if you have any comments or objection=
s
: > on this approach. The patches are:
: >
: > http://sites.google.com/site/cjayachandran/files/n32-toolchain.patc=
h
: > Toolchain support for N32
: > - Adds the linker emulations needed for n32
: > - Common preprocessor defines for ABI (_ABI_MIPS_SIM and _ABI???).
: > - Sets the long double type as 64 bit (this should be 128 bit in n3=
2,
: > but there is some work needed to get the 128 bit soft-float working=
).
: >
: > http://sites.google.com/site/cjayachandran/files/n32-kernel.patch
: > N32 compilation - makefiles and conf
: > - Adds ldscript.mips.n32.
: > - Some cleanup in Makefile.mips, add ABI flags
: > - bsd.cpu.mk CFLAGS for n32 compilation and linking
: >
: > I have introduced a TARGET_N32 similart to TARGET_64 for n32
: > compilation. =A0But I think on the long term, we need clean up the
: > different flags that affect architecture and ABI. Currently there i=
s
: > an overlap between the TARGET_CPUTYPE flag, the ISA_<arch> flags =A0=
and
: > the TARGET_<type> flags.
: >
: > Regards,
: > JC.
: > _______________________________________________
: > freebsd-mips@freebsd.org mailing list
: > http://lists.freebsd.org/mailman/listinfo/freebsd-mips
: > To unsubscribe, send any mail to "freebsd-mips-unsubscribe@freebsd.=
org"
: >
: _______________________________________________
: freebsd-mips@freebsd.org mailing list
: http://lists.freebsd.org/mailman/listinfo/freebsd-mips
: To unsubscribe, send any mail to "freebsd-mips-unsubscribe@freebsd.or=
g"
: =

: =




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100301.220611.787670930824834909.imp>