public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bje at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/26187] computed goto code does not produce jumps
Date: Thu, 09 Feb 2006 00:38:00 -0000	[thread overview]
Message-ID: <20060209003810.30338.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26187-602@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from bje at gcc dot gnu dot org  2006-02-09 00:38 -------
Thanks; I guess I misunderstood the semantics of computed gotos.  On closer
inspection of the GCC manual,

  "You may not use this mechanism to jump to code in a different function.
   If you do that, totally unpredictable things will happen.  The best way
   to avoid this is to store the label address only in automatic variables
   and never pass it as an argument."


-- 

bje at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26187


  parent reply	other threads:[~2006-02-09  0:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-09  0:29 [Bug middle-end/26187] New: " bje at gcc dot gnu dot org
2006-02-09  0:32 ` [Bug middle-end/26187] " pinskia at gcc dot gnu dot org
2006-02-09  0:38 ` bje at gcc dot gnu dot org [this message]
     [not found] <bug-26187-4@http.gcc.gnu.org/bugzilla/>
2024-03-16 17:54 ` 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=20060209003810.30338.qmail@sourceware.org \
    --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).