public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug exp/13206] support gcc's typeof Date: Wed, 22 Feb 2012 15:39:00 -0000 [thread overview] Message-ID: <bug-13206-4717-901OEC0xGA@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-13206-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=13206 Tom Tromey <tromey at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at redhat dot com --- Comment #1 from Tom Tromey <tromey at redhat dot com> 2012-02-22 15:36:58 UTC --- One wrinkle is that there's no way to tell if the source was compiled with GNU extensions. So, we can't simply parse "typeof" as a token. And, even the heuristic of looking up a symbol named "typeof" may fail if different source files were compiled with different options. __typeof__ seems reasonably easy, though there is the question of whether we'd want a new OP_TYPEOF. If not, it simplifies parsing, but you could have sizeof($x) != sizeof(typeof($x)) if $x changes between parsing and evaluation. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2012-02-22 15:39 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-20 21:41 [Bug exp/13206] New: " dje at google dot com 2012-02-22 15:39 ` tromey at redhat dot com [this message] 2012-02-22 17:10 ` [Bug exp/13206] " dje at google dot com 2012-02-22 20:50 ` tromey at redhat dot com 2012-06-28 15:39 ` tromey at redhat dot com 2012-07-19 15:39 ` cvs-commit at gcc dot gnu.org 2012-07-19 15:42 ` tromey at redhat 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-13206-4717-901OEC0xGA@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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: linkBe 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).