public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: Kriang Lerdsuwanakij <lerdsuwa@users.sourceforge.net>
Cc: Joe Buck <jbuck@synopsys.com>, gcc@gcc.gnu.org
Subject: Re: fix for PR 4447: is this really correct?
Date: Sat, 01 Dec 2001 17:32:00 -0000	[thread overview]
Message-ID: <orzo52l84s.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: Kriang Lerdsuwanakij's message of "Sat, 01 Dec 2001 14:10:08 +0700"

On Dec  1, 2001, Kriang Lerdsuwanakij <lerdsuwa@users.sourceforge.net> wrote:

> I have checked the ABI specifications
> (http://www.codesourcery.com/cxx-abi/abi.html)
> before starting on this patch.  And this bloat mangling behavior is
> what the ABI intended.

Right.  The C++ Standard paragraph referenced in that paragraph of the
ABI requires this behavior in the mangling of overloads of function
templates.  Constant folding is still applied to template arguments
*referenced* within the definition of the template function, before
overload resolution (in case of references to template functions) or
specialization resolution (in case of template classes), and encodings
of such referenced symbols may be constant-folded.  But the template
function names must enable one to tell the sequence of tokens used in
the template function definition, except for template argument names.

> (C++ Standard reference 14.5.5.1 p. 5.)

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me

  parent reply	other threads:[~2001-12-02  1:32 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-21 18:24 GCC 3.0.3 Mark Mitchell
2001-11-21 22:25 ` Joe Buck
2001-11-21 23:26   ` Mark Mitchell
2001-11-22  0:04     ` Joe Buck
2001-11-22  0:14       ` Mark Mitchell
2001-11-22  2:58         ` Joe Buck
2001-11-22  7:35           ` Mark Mitchell
2001-11-29 17:16             ` Mark Mitchell
2001-11-29 16:15           ` Joe Buck
2001-11-29 14:25         ` Mark Mitchell
2001-11-29 13:51       ` Joe Buck
2001-11-29 12:28     ` Mark Mitchell
2001-11-23 14:47   ` fix for PR 4447: is this really correct? Joe Buck
2001-11-24 20:36     ` Kriang Lerdsuwanakij
2001-11-30 23:02       ` Kriang Lerdsuwanakij
2001-12-01 16:08       ` Joe Buck
2001-12-02  3:12         ` Kriang Lerdsuwanakij
2001-12-03  9:42           ` Mark Mitchell
2001-12-01 17:32       ` Alexandre Oliva [this message]
2001-11-30 11:20     ` Joe Buck
2001-11-29 11:51   ` GCC 3.0.3 Joe Buck
2001-11-23 14:48 ` Stephane Carrez
2001-11-23 15:52   ` Jakub Jelinek
2001-11-30 11:47     ` Jakub Jelinek
2001-11-30 11:27   ` Stephane Carrez
2001-12-03  8:34   ` Mark Mitchell
2001-11-24 21:15 ` Toon Moene
2001-11-30 23:39   ` Toon Moene
2001-11-29 10:24 ` Mark Mitchell
2001-11-23 22:03 fix for PR 4447: is this really correct? mike stump
2001-11-24  5:14 ` Joe Buck
2001-11-30 16:20   ` Joe Buck
2001-11-30 15:23 ` mike stump
2001-12-03  9:49 ` Mark Mitchell
2001-12-03  9:53   ` Joe Buck
2001-12-03  9:56     ` Mark Mitchell
2001-11-24 15:40 mike stump
2001-11-30 18:14 ` mike stump
2001-12-01 16:14 ` Joe Buck
2001-12-03 15:40 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=orzo52l84s.fsf@free.redhat.lsd.ic.unicamp.br \
    --to=aoliva@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jbuck@synopsys.com \
    --cc=lerdsuwa@users.sourceforge.net \
    /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).