public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mathieu.malaterre at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/104363] hppa: __asm__ directive .global and multiple .symver not supported Date: Mon, 07 Feb 2022 08:18:40 +0000 [thread overview] Message-ID: <bug-104363-4-Y4Zq1O27ES@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104363-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104363 --- Comment #8 from Mathieu Malaterre <mathieu.malaterre at gmail dot com> --- Dear John, (In reply to John David Anglin from comment #6) > For context, see: > https://github.com/smuellerDD/libkcapi/issues/133#issuecomment-1024349323 > > Note that the following commit fixes the symbol issue on hppa with gcc-11: > https://github.com/smuellerDD/libkcapi/commit/ > 71d80bcffca26373149121e026d612146b4695d5 As mentionned in the commit message, this is an alternate solution (use of gcc-10 new attribute for `symver`). > The patch predates the hppa issue and it doesn't have anything to do > with hppa. It does mention -flto but this doesn't seem to apply here. Use of -flto seems to confict with the use of asm .symver directive, which is solved by using gcc attribute. > As far as I remember, support for symbol versioning is done in generic code. > > If I was to guess, I suspect the problem is with asm. Maybe a '\t' > is needed before .symver on hppa. The hppa assembler wants white space > before directives. That would not explain the regression gcc-10 -> gcc-11 AFAIK.
next prev parent reply other threads:[~2022-02-07 8:18 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-03 9:34 [Bug c/104363] New: " mathieu.malaterre at gmail dot com 2022-02-03 9:38 ` [Bug target/104363] " pinskia at gcc dot gnu.org 2022-02-03 9:45 ` mathieu.malaterre at gmail dot com 2022-02-03 9:47 ` mathieu.malaterre at gmail dot com 2022-02-03 11:18 ` pinskia at gcc dot gnu.org 2022-02-03 11:19 ` pinskia at gcc dot gnu.org 2022-02-03 17:13 ` danglin at gcc dot gnu.org 2022-02-03 17:32 ` dave.anglin at bell dot net 2022-02-07 8:18 ` mathieu.malaterre at gmail dot com [this message] 2022-02-07 8:20 ` mathieu.malaterre at gmail dot com 2022-02-22 9:15 ` mathieu.malaterre at gmail dot com 2022-02-22 14:42 ` dave.anglin at bell dot net
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-104363-4-Y4Zq1O27ES@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).