From: Tom Tromey <tromey@redhat.com>
To: Gabriel Dos Reis <gdr@integrable-solutions.net>
Cc: Diego Novillo <dnovillo@google.com>,
Richard Guenther <rguenther@suse.de>,
gcc-patches@gcc.gnu.org, Lawrence Crowl <crowl@google.com>,
bonzini@gnu.org, dj@redhat.com,
laurynas.biveinis@gmail.com, gdb@sourceware.org,
Keith Seitz <keiths@redhat.com>
Subject: Re: Merge C++ conversion into trunk (0/6 - Overview)
Date: Wed, 15 Aug 2012 18:21:00 -0000 [thread overview]
Message-ID: <87zk5wt3rz.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAAiZkiDhQ3VwYUYnV=rwL1tVUzxkV9Uf5J5Zmjth=cJ0tXkc_Q@mail.gmail.com> (Gabriel Dos Reis's message of "Wed, 15 Aug 2012 13:02:11 -0500")
>>>>> "Gaby" == Gabriel Dos Reis <gdr@integrable-solutions.net> writes:
Tom> I asked Keith to resurrect his patch for this.
Gaby> Since people are concerned about typing rules, would it
Gaby> be an option for GDB to allow people to input pointer
Gaby> literals with the "p" suffix (or "0p" prefix instead of "0x")?
I think on the whole I'd rather have one extension instead of two.
It seems to me that the above would still require extensions in the
overloading code, to deal with conversions from void*; or perhaps some
magic pointer type.
What I think Keith is going to do is take his patch, change it so that
int->pointer conversions (if the int != 0) are given a different badness
from other conversions (meaning that, in theory, this should only be
chosen as a last resort, and shouldn't interfere with ordinary uses),
and finally add a parameter so that the feature can be disabled.
I hope this will be acceptable all around.
Tom
next prev parent reply other threads:[~2012-08-15 18:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120812200427.GA12561@google.com>
2012-08-15 12:01 ` Richard Guenther
2012-08-15 12:19 ` Diego Novillo
2012-08-15 12:21 ` Richard Guenther
2012-08-15 12:23 ` Diego Novillo
2012-08-15 15:13 ` Jan Kratochvil
2012-08-15 15:44 ` Michael Matz
2012-08-15 15:50 ` Jan Kratochvil
2012-08-15 16:39 ` Jakub Jelinek
2012-08-15 16:00 ` Diego Novillo
2012-08-15 17:54 ` Tom Tromey
2012-08-15 18:02 ` Gabriel Dos Reis
2012-08-15 18:21 ` Tom Tromey [this message]
2012-08-15 18:26 ` Gabriel Dos Reis
2012-08-17 17:45 ` Keith Seitz
2012-08-17 17:56 ` H.J. Lu
2012-08-15 14:25 ` Mike Stump
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=87zk5wt3rz.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=bonzini@gnu.org \
--cc=crowl@google.com \
--cc=dj@redhat.com \
--cc=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=gdr@integrable-solutions.net \
--cc=keiths@redhat.com \
--cc=laurynas.biveinis@gmail.com \
--cc=rguenther@suse.de \
/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).