From: Piotr Kubaj <pkubaj@anongoth.pl>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Gerald Pfeifer <gerald@pfeifer.com>,
gcc-patches@gcc.gnu.org, David Edelsohn <dje.gcc@gmail.com>,
Andreas Tobler <andreast@freebsd.org>
Subject: Re: rs6000: add support for powerpc64le-unknown-freebsd
Date: Thu, 29 Apr 2021 13:37:46 +0200 [thread overview]
Message-ID: <YIqailv4U424yEUH@KGPE-D16> (raw)
In-Reply-To: <20201216222309.GM2672@gate.crashing.org>
[-- Attachment #1: Type: text/plain, Size: 1899 bytes --]
Hello again,
sorry to reopen this issue, but one part was skipped. It was just now found out, because it doesn't cause build issues, but only runtime issues (GCC fails to build binaries):
/usr/local/bin/ld: /usr/local/lib/gcc10/libgcc_s.so: undefined reference to `.__udivmodti4'
/usr/local/bin/ld: /usr/local/lib/gcc10/libgcc_s.so: undefined reference to `.__ctzdi2'
/usr/local/bin/ld: /usr/local/lib/gcc10/libgcc_s.so: undefined reference to `.__parityti2'
/usr/local/bin/ld: /usr/local/lib/gcc10/libgcc_s.so: undefined reference to `.__enable_execute_stack'
Could you commit the following patch:
--- gcc/configure.orig 2021-04-29 10:19:44 UTC
+++ gcc/configure
@@ -29405,7 +29405,7 @@ $as_echo "#define HAVE_LD_PPC_GNU_ATTR_LONG_DOUBLE 1"
esac
case "$target:$tm_file" in
- powerpc64-*-freebsd* | powerpc64*-*-linux* | powerpc*-*-linux*rs6000/biarch64.h*)
+ powerpc64*-*-freebsd* | powerpc64*-*-linux* | powerpc*-*-linux*rs6000/biarch64.h*)
case "$target" in
*le-*-linux*)
emul_name="-melf64lppc"
--- gcc/configure.ac.orig 2021-04-29 11:22:30 UTC
+++ gcc/configure.ac
@@ -5871,7 +5871,7 @@ EOF
esac
case "$target:$tm_file" in
- powerpc64-*-freebsd* | powerpc64*-*-linux* | powerpc*-*-linux*rs6000/biarch64.h*)
+ powerpc64*-*-freebsd* | powerpc64*-*-linux* | powerpc*-*-linux*rs6000/biarch64.h*)
case "$target" in
*le-*-linux*)
emul_name="-melf64lppc"
Thanks,
Piotr Kubaj.
On 20-12-16 16:23:09, Segher Boessenkool wrote:
> On Tue, Dec 15, 2020 at 12:52:05AM +0100, Piotr Kubaj wrote:
> > Yes, there is, thanks for noticing that!
> >
> > Fixed patch attached.
>
> Hi!
>
> Could you send this as plain text? It now is quoted-printable, which is
> really hard to handle.
>
> Thanks!
>
> Hrm, this is really short, I'll just try to fix it by hand... Wish me
> luck :-)
>
>
> Segher
--
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-04-29 11:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 15:35 Piotr Kubaj
2020-12-14 16:46 ` Segher Boessenkool
2020-12-14 23:29 ` Gerald Pfeifer
2020-12-15 0:30 ` Segher Boessenkool
2020-12-16 22:58 ` Segher Boessenkool
2020-12-28 11:44 ` Gerald Pfeifer
2020-12-28 12:37 ` Segher Boessenkool
2021-09-10 23:26 ` Piotr Kubaj
2020-12-14 23:37 ` Gerald Pfeifer
2020-12-14 23:52 ` Piotr Kubaj
2020-12-16 22:23 ` Segher Boessenkool
2021-04-29 11:37 ` Piotr Kubaj [this message]
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=YIqailv4U424yEUH@KGPE-D16 \
--to=pkubaj@anongoth.pl \
--cc=andreast@freebsd.org \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=segher@kernel.crashing.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 read-only IMAP folder(s) and NNTP newsgroup(s).