Date: Mon, 09 Mar 2020 04:42:10 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 214404] base/gcc: and base/binutils -r424540 for TARGET_ARCH=powerpc64 example: file placement and gcc/g++ internal file lookups do not match so gcc/g++ do not work Message-ID: <bug-214404-7788-4MhoDGmjwW@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-214404-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-214404-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214404 --- Comment #5 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Mark Millard from comment #4) Adding a side note: With the clang conversion as it is, FreeBSD switched from -msvr4-struct-return to -maix-struct-return for powerpc64. gcc by default is still -msvr4-struct-return for powerpc64. If ABI compatibility is the primary criteria, it is not obvious to me which side changes but one should. Without ABI compatibility, base/gcc*'s may be irrelevant for powerpc64. https://reviews.llvm.org/D73290 is a review for changing the clang side (restoring the historical FreeBSD ABI behavior on the specific issue). But the review has had no activity after late 2020-Jan. The change might make the claim "OpenPOWER ELF V2 ABI" odd in that it does not match linux (but does match embedded or whatever the terminology was). (The OpenPower ABI is a case analysis, not uniform.) (I tested and reported. But it would not be for me to declare such is the FreeBSD direction. I am actually still using the change in order to allow safely mixing gcc and clang materials in non-kernel areas.) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-214404-7788-4MhoDGmjwW>