From: Mark Mitchell <mark@codesourcery.com>
To: aoliva@redhat.com
Cc: wilson@cygnus.com, gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org,
gdb@sources.redhat.com
Subject: Re: C++ ptrmemfun break if FUNCTION_BOUNDARY < 2 *BITS_PER_UNIT
Date: Tue, 10 Apr 2001 09:27:00 -0000 [thread overview]
Message-ID: <20010410092712A.mitchell@codesourcery.com> (raw)
In-Reply-To: <orofu6xfro.fsf@guarana.lsd.ic.unicamp.br>
I think this all makes sense.
I should have thought of this issue when implementing the new ABI;
somehow, it didn't occur to me.
I would sugest that if you're going to use an enum to represent
different choices about representation here (which seems reasonable)
that you have the TARGET_ macro evaluate to an enum, rather than a
boolean. That would be simpler. Have it default to
ptrmemfunc_vbit_in_pfn in defaults.h, and then you can eliminate the
conditional compilation in decl.c.
Thank you for taking on the task of fixing the problem.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~2001-04-10 9:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-06 3:14 C++ ptrmemfun break if FUNCTION_BOUNDARY < 2 * BITS_PER_UNIT Alexandre Oliva
2001-04-06 10:53 ` Neil Booth
2001-04-06 11:03 ` Alexandre Oliva
2001-04-07 4:52 ` Richard Earnshaw
2001-04-07 10:12 ` Dave Korn
2001-04-06 13:05 ` Jim Wilson
2001-04-06 14:45 ` DJ Delorie
2001-04-09 8:19 ` Alexandre Oliva
2001-04-09 12:28 ` Joern Rennecke
2001-04-09 13:12 ` Alexandre Oliva
2001-04-09 13:43 ` Joern Rennecke
2001-04-18 5:48 ` Richard Earnshaw
2001-04-18 12:11 ` Alexandre Oliva
2001-04-10 9:27 ` Mark Mitchell [this message]
2001-04-17 10:38 ` Andrew Cagney
2001-04-17 13:02 ` Daniel Berlin
2001-05-16 4:53 ` Jason Merrill
2001-05-16 7:18 ` Daniel Berlin
2001-04-06 3:34 dewar
2001-04-06 4:41 ` Jamie Lokier
2001-04-06 6:02 ` Joern Rennecke
2001-04-06 4:49 dewar
2001-04-06 5:00 ` Alexandre Oliva
2001-04-06 5:05 dewar
2001-04-06 5:10 ` Jamie Lokier
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=20010410092712A.mitchell@codesourcery.com \
--to=mark@codesourcery.com \
--cc=aoliva@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=wilson@cygnus.com \
/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).