public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sds at gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/35708]  New: jump to label enters catch block
Date: Wed, 26 Mar 2008 18:57:00 -0000	[thread overview]
Message-ID: <bug-35708-10080@http.gcc.gnu.org/bugzilla/> (raw)

uname -a
SunOS neron 5.9 Generic_112233-08 sun4u sparc SUNW,Sun-Fire-480R
g++ --version
g++ (GCC) 4.2.1

the following program fails with the error
======================================= zot.cc =================
int alloccount = 100;

struct object { int one_o; int allocstamp; };
    struct gcv_object_t {
      int one_o;
      /* Conversion to object. */
      operator object () const;
      /* Conversion from object. */
      gcv_object_t (object obj);
      /* Conversion from fake_gcv_object. */
      gcv_object_t (struct fake_gcv_object obj);
      /* Uninitialized object. */
      gcv_object_t ();
    };

  static inline int pgci_pointable (object obj) {
    return obj.one_o;
  }
  static inline int pgci_pointable (gcv_object_t obj) {
    return obj.one_o;
  }

gcv_object_t STACK[1];

int main (int argc, char *argv[]) {

  check_rehash_size: {
        if ((pgci_pointable(STACK[0]) ==
pgci_pointable((((object){one_o:(((int)(int)(((0 << 3) + 7UL)) << 0) +
((int)(int)(0) << 7)), allocstamp: alloccount}))))) {
         bad_rehash_size:
          goto check_rehash_size;
      }
       goto bad_rehash_size;
 }
}
======================================= zot.cc =================
$ g++ -c zot.cc
zot.cc: In function 'int main(int, char**)':
zot.cc:30: error: jump to label 'bad_rehash_size'
zot.cc:33: error:   from here
zot.cc:29: error:   enters catch block

I don't see any catch blocks here.
thanks.


-- 
           Summary: jump to label enters catch block
           Product: gcc
           Version: 4.2.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: sds at gnu dot org


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


             reply	other threads:[~2008-03-26 18:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-26 18:57 sds at gnu dot org [this message]
2008-03-26 20:39 ` [Bug c++/35708] " rguenth at gcc dot gnu dot org
2008-03-26 20:44 ` sds at gnu dot org
2008-03-28 22:47 ` bruno at clisp dot org
2008-03-28 22:48 ` bruno at clisp dot org
2008-03-29 10:53 ` rguenth at gcc dot gnu dot org
2008-03-29 10:57 ` rguenth at gcc dot gnu dot org
2008-03-29 15:13 ` jason at gcc dot gnu dot org
2008-03-29 15:20 ` jason at gcc dot gnu dot org
2008-04-09 16:17 ` jason at gcc dot gnu dot org
2008-04-09 19:58 ` jason at gcc dot gnu dot org
2008-04-09 20:11 ` jason at gcc dot gnu dot org
2008-04-11 21:28 ` pinskia at gcc dot gnu dot org
2008-04-11 21:29 ` [Bug c++/35708] [4.2 Regression] " pinskia at gcc dot gnu dot org
2008-05-19 20:35 ` jsm28 at gcc dot gnu dot org
2008-12-02 17:24 ` jason at gcc dot gnu dot 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-35708-10080@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).