Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 1 Apr 2015 16:37:21 -0700
From:      Mark Millard <markmi@dsl-only.net>
To:        Warner Losh <imp@bsdimp.com>
Cc:        FreeBSD Toolchain <freebsd-toolchain@freebsd.org>, FreeBSD PowerPC ML <freebsd-ppc@freebsd.org>
Subject:   Re: Shorter report: powerpc64-xtoolchain-gcc use fails from powerpc (non-64)
Message-ID:  <7AF12D5F-F4A0-429E-AEAE-4AEF2D35FE31@dsl-only.net>
In-Reply-To: <B49E8B91-B8C2-4F0C-9662-8814C16041A4@bsdimp.com>
References:  <BB07709E-A5D3-458A-8ED7-61E64103A43C@dsl-only.net> <B49E8B91-B8C2-4F0C-9662-8814C16041A4@bsdimp.com>

next in thread | previous in thread | raw e-mail | index | archive | help

On 2015-Apr-1, at 02:49 PM, Warner Losh <imp at bsdimp.com> wrote:


>> On Apr 1, 2015, at 2:44 PM, Mark Millard <markmi@dsl-only.net> wrote:
>>=20
>> Attempting to use CROSS_TOOLCHAIN=3Dpowerpc64-gcc on powerpc (non-64) =
11.0-CURRENT with TARGET_ARCH=3Dpowerpc64 gets:
>>=20
>>> --- crti.o ---
>>> gcc -O2 -pipe   -I/usr/srcC/lib/csu/powerpc64/../common  =
-I/usr/srcC/lib/csu/powerpc64/../../libc/include  -mlongcall -std=3Dgnu99 =
 -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter =
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type =
-Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter =
-Wcast-align -Wchar-subscripts -Winline -Wnested-externs =
-Wredundant-decls -Wold-style-definition -Wno-pointer-sign    -c =
/usr/srcC/lib/csu/powerpc64/crti.S
>>> ...
>>> /usr/srcC/lib/csu/powerpc64/crti.S: Assembler messages:
>>> /usr/srcC/lib/csu/powerpc64/crti.S:35: Error: junk at end of line, =
first unrecognized character is `@'
>>> /usr/srcC/lib/csu/powerpc64/crti.S:51: Error: junk at end of line, =
first unrecognized character is `@'
>>> *** [crti.o] Error code 1
>>>=20
>>=20
>>=20
>>=20
>> Read below only for analysis.
>>=20
>>=20
>>=20
>> First I'll deal with the error messages. Then I'll deal with the =
"gcc".
>>=20
>> The lines of crti.S in question are:
>>=20
>>>     .quad   .L._init,.TOC.@tocbase,0
>>> ...
>>>     .quad   .L._fini,.TOC.@tocbase,0
>>=20
>> The error messages are because __powerpc64__ is not defined when =
machine/asm.h is included so the wrong definition is used for =
_ENTRY(=E2=80=A6):
>=20
> The gcc port needs to be fixed, with changes fed upstream.

The head/lib/csu/powerpc64/Makefile generated "gcc" as the command (see =
above). That in turn ended up as using: /usr/bin/gcc , which is the =
FreeBSD 4.2.1 system gcc.

So no port was involved. That may be the (or a) problem: ${XCC} was not =
being used.


>>> #ifdef __powerpc64__
>>> ...
>>> #define _ENTRY(name) \
>>>      .section ".text"; \
>>>      .p2align 2; \
>>>      .globl  name; \
>>>      .section ".opd","aw"; \
>>>      .p2align 3; \
>>>      name: \
>>>      .quad   DOT_LABEL(name),.TOC.@tocbase,0; \
>>>      .previous; \
>>>      .p2align 4; \
>>>      TYPE_ENTRY(name) \
>>> DOT_LABEL(name):
>>> ...
>>> #else /* !__powerpc64__ */
>>> #define _ENTRY(name) \
>>>      .text; \
>>>      .p2align 4; \
>>>      .globl  name; \
>>>      .type   name,@function; \
>>>      name:
>>> #define _END(name)
>>> #endif /* __powerpc64__ */
>>=20
>> The (powerpc64 specific) Makefile may need to force a 64-bit usage =
(-m64 ?), presuming that such is supported from the 32 bit environment.
>=20
> Generally, we=E2=80=99ve not added those kinds of flags to the command =
line. There=E2=80=99s many subtle issues in the tree trying to do =
that=E2=80=A6
>=20
> Warner

=46rom a powerpc (non-64) 11.0-CURRENT boot is the following supposed to =
work by producing a powerpc64 appropriate result (no CROSS_TOOLCHAIN for =
this question)?=20

make buildworld buildkernel KERNCONF=3DGENERIC64 TARGET=3Dpowerpc =
TARGET_ARCH=3Dpowerpc64



The standard v4.2.1 /usr/bin/gcc in a powerpc context (non-64) for that =
make command would produce files for TARGET_ARCH=3Dpowerpc unless the =
command lines specified otherwise.

Notably the build environment is picking powerpc64 specific paths when =
appropriate, such as:

lib/csu/powerpc64/Makefile

so that specific Makefile is not likely to be used when powerpc64 =
handling is inappropriate, even executed from from a powerpc (non-64) =
context. A different path (and so a distinct Makefile) would be used for =
KERNCONF=3DGENERIC TARGET_ARCH=3Dpowerpc .


=3D=3D=3D
Mark Millard
markmi at dsl-only.net




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7AF12D5F-F4A0-429E-AEAE-4AEF2D35FE31>