public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/112870] incorrect jmp when using goto on a function, causing infinite loop
Date: Tue, 05 Dec 2023 19:04:45 +0000	[thread overview]
Message-ID: <bug-112870-4-HfAkt6Xn3U@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112870-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
What you are doing is all not allowed with this extension.

Yes the documentation should be a little clearier on this but at least the part
where it says:
`You may not use this mechanism to jump to code in a different function.`

Is very clear on that part.

Basically computed gotos can only go to labels in the same function whos
address has been taken. That is the effect you are seeing here and why the
difference comes from.

  parent reply	other threads:[~2023-12-05 19:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 18:41 [Bug c/112870] New: " grantrwittmann at gmail dot com
2023-12-05 18:44 ` [Bug c/112870] " pinskia at gcc dot gnu.org
2023-12-05 19:01 ` grantrwittmann at gmail dot com
2023-12-05 19:04 ` pinskia at gcc dot gnu.org [this message]
2024-03-16 17:58 ` 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-112870-4-HfAkt6Xn3U@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).