public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bouanto at zoho dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug jit/100380] Segfault when using inline asm
Date: Sat, 15 May 2021 14:13:45 +0000	[thread overview]
Message-ID: <bug-100380-4-pJNP1ScovD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100380-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100380

--- Comment #4 from Antoni <bouanto at zoho dot com> ---
I just had a similar issue when developing a new feature for libgccjit and it
might be the same problem. If it is (I haven't checked in this case), here's
what's happening:

 * The asm is replayed.
 * The asm tries to access the replayed variable (which wasn't replayed yet
because it was created after the asm).
 * Segfault (the rest is not executed, but is shown to explain what's
happening)
 * The variable is replayed (too late because it was NULL when accessed by the
asm).

Again it's to be verified, and I'm not sure what should be the solution to this
problem because the mementos are replayed in the order they were created.

  parent reply	other threads:[~2021-05-15 14:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-02  1:51 [Bug jit/100380] New: " bouanto at zoho dot com
2021-05-02  1:54 ` [Bug jit/100380] " bouanto at zoho dot com
2021-05-02  2:20 ` bouanto at zoho dot com
2021-05-11 12:04 ` marxin at gcc dot gnu.org
2021-05-15 14:13 ` bouanto at zoho dot com [this message]
2021-05-16 13:54 ` bouanto at zoho dot com
2021-08-16 11:31 ` marxin at gcc dot gnu.org
2021-09-13 22:31 ` bouanto at zoho dot com

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-100380-4-pJNP1ScovD@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).