public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "miladfarca at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/107736] call to a function, generated by inline asm, is off by one byte
Date: Thu, 17 Nov 2022 19:39:20 +0000 [thread overview]
Message-ID: <bug-107736-4-zIe7CN966t@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107736-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107736
--- Comment #2 from mfarca <miladfarca at gmail dot com> ---
> Toplevel inline-asm will be emitted without any knowledge of the current section.
So this is a limitation of gcc I guess? as clang does have the knowledge on
which is which.
The main issue still persists as call is made to the wrong address.
next prev parent reply other threads:[~2022-11-17 19:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 19:21 [Bug c/107736] New: " miladfarca at gmail dot com
2022-11-17 19:34 ` [Bug c/107736] " pinskia at gcc dot gnu.org
2022-11-17 19:39 ` miladfarca at gmail dot com [this message]
2022-11-17 19:43 ` pinskia at gcc dot gnu.org
2022-11-17 19:50 ` miladfarca at gmail dot com
2022-11-17 19:58 ` pinskia at gcc dot gnu.org
2022-12-04 5:37 ` pinskia 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-107736-4-zIe7CN966t@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: 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).