public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/98482] -mfentry creates invalid call for -mcmodel=large Date: Fri, 08 Jan 2021 09:34:12 +0000 [thread overview] Message-ID: <bug-98482-4-6hYtcrTMUi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98482-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98482 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> --- If we are emitting for nested functions pushq %r10 1: call __fentry__ popq %r10 (is it ok to misalign the stack for __fentry__? but then even plain call __fentry__ actually misaligns it), then perhaps we can do similarly for the PIC case. But I wonder how does __fentry__ then find the caller if it can't rely on the return address being right above the return address to the function that called __fentry__ (appart from unwind info of course, but we don't really emit .cfi_* directives here either, do we?).
next prev parent reply other threads:[~2021-01-08 9:34 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-30 19:13 [Bug c/98482] New: " toiwoton at gmail dot com 2021-01-07 10:44 ` [Bug target/98482] " crazylht at gmail dot com 2021-01-07 12:01 ` ubizjak at gmail dot com 2021-01-07 12:24 ` ubizjak at gmail dot com 2021-01-07 13:30 ` toiwoton at gmail dot com 2021-01-07 13:37 ` ubizjak at gmail dot com 2021-01-07 23:50 ` hjl.tools at gmail dot com 2021-01-08 2:08 ` crazylht at gmail dot com 2021-01-08 8:58 ` toiwoton at gmail dot com 2021-01-08 9:29 ` ubizjak at gmail dot com 2021-01-08 9:34 ` jakub at gcc dot gnu.org [this message] 2021-01-08 12:54 ` cvs-commit at gcc dot gnu.org 2021-01-08 14:48 ` cvs-commit at gcc dot gnu.org 2021-01-08 14:49 ` hjl.tools at gmail dot com 2021-01-08 14:50 ` ubizjak at gmail dot com 2021-01-08 16:47 ` cvs-commit 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-98482-4-6hYtcrTMUi@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).