public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libffi/102874] [12 regression] src/x86/win64.S doesn't assemble with Solaris as Date: Mon, 15 Nov 2021 09:30:13 +0000 [thread overview] Message-ID: <bug-102874-4-gH6Ttyj8P1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102874-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102874 --- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Rainer Orth <ro@gcc.gnu.org>: https://gcc.gnu.org/g:a91f844ef449d0dd1cf2e0e47b0ade0d8a6304e1 commit r12-5262-ga91f844ef449d0dd1cf2e0e47b0ade0d8a6304e1 Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> Date: Mon Nov 15 10:24:27 2021 +0100 libffi: Use #define instead of .macro in src/x86/win64.S [PR102874] The libffi 3.4.2 import badly broke Solaris/x86 bootstrap with the native assembler: Assembler: "/vol/gcc/src/hg/master/local/libffi/src/x86/win64.S", line 88 : Illegal mnemonic Near line: ".macro epilogue" "/vol/gcc/src/hg/master/local/libffi/src/x86/win64.S", line 88 : Syntax error Near line: ".macro epilogue" "/vol/gcc/src/hg/master/local/libffi/src/x86/win64.S", line 95 : Illegal mnemonic Near line: ".endm" "/vol/gcc/src/hg/master/local/libffi/src/x86/win64.S", line 95 : Syntax error Near line: ".endm" "/vol/gcc/src/hg/master/local/libffi/src/x86/win64.S", line 100 : Illegal mnemonic Near line: " epilogue" "/vol/gcc/src/hg/master/local/libffi/src/x86/win64.S", line 100 : Syntax error Near line: "epilogue" Solaris as doesn't support .macro/.endm. Fixed by using #define instead of the unportable .macro. Tested on i386-pc-solaris2.11 and x86_64-pc-linux-gnu. The bug has been reported upstream (https://github.com/libffi/libffi/issues/665); a corresponding pull request is also pending (https://github.com/libffi/libffi/pull/669). 2021-10-21 Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> libffi: PR libffi/102874 * src/x86/win64.S (epilogue): Use #define instead of .macro.
next prev parent reply other threads:[~2021-11-15 9:30 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-21 9:36 [Bug libffi/102874] New: " ro at gcc dot gnu.org 2021-10-21 9:38 ` [Bug libffi/102874] " ro at gcc dot gnu.org 2021-10-21 9:38 ` ro at gcc dot gnu.org 2021-10-21 11:24 ` hjl.tools at gmail dot com 2021-10-21 21:10 ` ro at CeBiTec dot Uni-Bielefeld.DE 2021-10-21 22:09 ` hjl.tools at gmail dot com 2021-11-05 13:47 ` rguenth at gcc dot gnu.org 2021-11-05 15:08 ` hjl.tools at gmail dot com 2021-11-13 1:39 ` hp at gcc dot gnu.org 2021-11-13 6:31 ` hjl.tools at gmail dot com 2021-11-15 9:17 ` ro at gcc dot gnu.org 2021-11-15 9:30 ` cvs-commit at gcc dot gnu.org [this message] 2021-11-15 9:42 ` ro at gcc dot gnu.org
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=bug-102874-4-gH6Ttyj8P1@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).